cancel
Showing results for 
Search instead for 
Did you mean: 

Problem on setup using IAS with on-premise corporate Active Directory

umberto_panico
Participant
0 Kudos

Hi All,

in order to achieve this configuration (without conditional authentication), we have two problems when we try to login.

1) IAS Side log:

2021-07-15 16:30:20.000 UTC,"<IP>",anonymous,ERROR,"74E2EAD0-118C-4A82-959F-B659FAE53A4D","Authentication failure when calling CorporateUserStore.Can not perform http request to: https://proxysci-<tenant>.eu2.hana.ondemand.com/rest/v1/users/<user>; Caused by: 503 : [<!doctype html><html lang=""en""><head><title>HTTP Status 503  Service Unavailable</title><style type=""text/css"">body {font-family:Tahoma,Arial,sans-serif

2021-07-15 16:30:20.000 UTC,"<IP>",anonymous,ERROR,"74E2EAD0-118C-4A82-959F-B659FAE53A4D","Unexpected failure when calling CorporateUserStore connector for user '<user>'. Result details - status code: 503 SERVICE_UNAVAILABLE

2) SAP Cloud Connector Side

Caused by:
javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr:
DSID-0C090417, comment: AcceptSecurityContext error, data 52e, v1db1 ]

 at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3154)

Very very strange, because from SCC we able to simulate authentication via LDAP.

We have followed the documentation and created an incident but are unable to resolve it

Thanks 1K!

Accepted Solutions (0)

Answers (3)

Answers (3)

istvanbokor
Advisor
Advisor

Hello,

In IAS proxy logs I can see the error:

Could not read the SCIM response. Error details: response code: 401; response: { "Errors": [ { "description": "Authentication to LDAP failed", "code": "401" }

This error means a wrong user/password. Have in mind that the first logon requires the Login Name only (Login Name on IAS = sAMAccountname on AD).

Best regards,
Istvan

umberto_panico
Participant

not this.

We are in contct with SAP, I will update this post as soon is successfully completed

todor_petrov
Contributor
0 Kudos

Hello, a possible solution is explained in this SAP Note -> https://launchpad.support.sap.com/#/notes/0002953747

For us it solved the issue.

todor_petrov
Contributor
0 Kudos

Same issue here. Please update if you find a solution.