error in UWL registering: User is missing credentials for alias

[Former Member]

Hi Gurus,

I have a peculiar issue on my system.

- I'm created an ID in ECC6 R/3 side with SAP_ALL

- I've also linked the Portal UME from ECC6. So login IDs are created from ECC SU01.

- Able to log in to portal from the ID.

- ID given portal administrator roles.

But when I try to register a Webflow connector with a System Alias with UWL. I get the error:

(Connector) :com.sap.netweaver.bc.uwl.connect.ConnectorException:<Date/Timestamp>

(Connector) :com.sap.portal.connectivity.destinations.PortalDestinationsServiceException:User is missing credentials for connecting to alias <SID_ALIAS>. Contact your system administrator.

I checked the trace files:

User :<USER.R3_DATASOURCE.<USERID>> getting data from system : <SID_ALIAS>: JCO error in reading configuration:<Date/Timestamp>:com.sap.portal.connectivity.destinations.PortalDestinationsServiceException: User is missing credentials for connecting to alias <SID_ALIAS>. Contact your system administrator.

Some of the things I've done:

- Ensure SID_ALIAS is correct.

- Ensure JCO are correct

- include the Portal ACL in R/3 via STRUSTSSO2

- Ensure permission of SID_ALIAS is set to end user

Any more suggestions? Thanks in advance...

[Former Member · Accepted solution]

Hi Jansen,

have you checked the user in SU01 and made sure he has the right authorizations in the ECC system?

regards,

Dion

[Former Member]

Hi all,

Thanks for you help..... I found the problem to be an embarrassing elementary issue.

The Logon Group for SID_ALIAS is mispelt.

Thanks all for their valuable input. Points awarded.

[Former Member]

Hi Jansen:

Can You tell me please How did You Solve this issue?

I hope you can help me.

Thank you

[Former Member]

Hi Jansen,

I've the same issue. Could you explain where you found the mispelt Logon-Group for the system alias?

Best Regards

Dominik

[Former Member]

Hi,

> User is missing credentials for connecting to alias <SID_ALIAS>

shows the user mapping issue for the system alias. Recheck that and then check user management property from System properties. It is not necessary that Portal and backend should be on same machine always. System concept means connecting to different SAP systems. Portal can connect to client 200 via JCo connection you have maintained.

Check this thread.

Check the UWL configuration guide also

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a3461636-0301-0010-3787-978f5ac8...

Regards,

Harini S

[Former Member]

Is SID_ALIAS assigned to a system object that points to the same place that you are creating the user? This could happen because your Portal UME points to say client 100 in the back-end, but your SID_ALIAS is assigned to a system object that points to client 200. Since the user exists in 100 but not in 200, then the JCo SSO will fail connecting to the back-end.

[Former Member]

Thank all for the reply.

I've check SU01 and given SAP_ALL, I've also set super admin to the ID, still having the same problem.

Just a bit of a detail.

My backend is configured to use CUA.

My portal UME is client 100 which is the CUA client. But SID_ALIAS is configure to client 200. I created the ID in client 100 and gave access to both client 100 and 200 with same password and SAP_ALL.

anyone know which JCO does the registration of the UWL use? could that be the problem?

so far I set SAP_R3_HumanResources and SAP_R3_SelfServiceGenerics to client 200. Individual test for the JCO is ok.

[Former Member]

Hi,

Looks like a permission issue. Can you try this with user having super_admin_role.

Regards

Deb