By: Qasim Baqri user 12 Oct 2015 at 1:37 a.m. CDT

1 Response
Qasim Baqri gravatar
We are trying modify user information using SCIM api's We tried with the below commands to get user info. 1. curl -v -k --request GET -H "Accept: application/json" -H "Authorization: Bearer fd6210a2-f491-45c8-8622-c15301aea201" 'https://localhost:1636/oxTrust/seam/resource/restv1/Users/@!5384.B1CC.C70F.CB32!0001!0FC6.630D!0008!2104.0FA0' 2. curl -v -k --request GET --user admin:abc123 -H "Accept: application/json" 'https://localhost:1636/oxTrust/seam/resource/restv1/Users/@!5384.B1CC.C70F.CB32!0001!0FC6.630D!0000!2732.BFBC' But every time we get an error that we were unable to figure out. "0� � x� z * Connection #0 to host localhost left intact � YCannot decode the provided ASN.1 sequence as an LDAP message because the first element of the sequence could not be decoded as an integer message ID: org.opends.server.protocols.asn1.ASN1Exception: Cannot decode the provided ASN.1 integer element because the length of the element value was not between one and four bytes (actual length was 32)�" Can you please let us know what we are doing wrong.

By Michael Schwartz Account Admin 12 Oct 2015 at 9:06 a.m. CDT

Michael Schwartz gravatar
1) Why are you trying to use port 1636 for SCIM? That is the LDAP port... So of course LDAP cannot understand the SCIM protocol. SCIM interfaces are provided by oxTrust, which runs on 443. 2) In the second request, I don't understand why you are passing the admin creds. In SCIM, you should create a Custom Interception Script Authorization policy that allows your client to call the SCIM API. 3) I see the Bearer token, how did you obtain this token? Please read carefully the [Gluu Sever Admin Guide]( and the [Gluu Server SCIM Reference](