Hi Team,

We have recently upgraded webMethods from 7.1 to 9.5 SP1 and facing an interesting and wierd issue with HTTPS port which is opened for a client application. While trying to access webMethods service using https port, user at client application is receiving the error as Access denied.

We had followed all the required procedures as part of allowing service under HTTPS Ports

1. Initially userid has been created for an ACL under which we have allowed the webMethods service under HTTPS port. Same userid/password are being used in client application as part of Basic Authentication.
2. SSL Port has been opened at Firewall and requests are coming through webMethods end.
3. When we are directly accessing the flow service using https invoke, service is getting executed without any issue, however only when we are trying to access the same from client application, we are facing an access denied issue.

We suspect that there is no setting that has to be updated as part of webMethods Upgradation/Migration.

Any pointer in this regards is much helpful.

Many

Hi Suresh,

Have you checked the Access Mode of the HTTPS port? Is it Access Mode Global (Allow by Default*) ?

HTH.

Thanks,
Rankesh

Hi Rankesh,

IP Access and Access Mode both are “Allow by Default”.

Regards
Suresh

Hi Suresh,

Please check the ACL of the service, invoked by client on HTTPS port.

HTH.

Thanks,
Rankesh

@ Suresh,

How is your client application accessing your flow service. Is the ACL properties set like execute ACL…?

I see your are receiving the access denied error. Is your client application invoking your flow service with right credentials?

Hi Mahesh,

Execute ACLs are set for the service which is allowed in HTTPS port.

Client application is sending valid credentials along with the request.

FYI, the same service is working/executing fine in 7.1 Environment but not in 9.5 Env. Looking for some pointer at configuration/extended settings end where there is change as part of Upgradation.

Regards
Suresh Kumar

Hi Suresh,

Please change the HTTP log facility to trace and capture the incoming request. Please share the log to know more about the issue.

Thanks,
Rankesh

SSL handshake may not be done as earlier version. If the client system is using username/password for authentication, you may try to open an HTTPS port with: Client Authentication = Username/password instead of Request Client Cert.

Hello mates,

Thanks for your response.

After verifying the client properties, we came to know that WmRealm value that being used by client is “webMethods” but the same has been updated to “Integration Server” from webM 8.2.2 (or 9.0).

After updating the WmRealm value to Integration Server in Client’s property file, connection has been established which resolved this issue.