Hi, has anyone made experience with the API implementation? We try to get user information via API call but it always ends in error: 404 - File or directory not found. The documentation doesn#t clearly state what attribute is needed for {useridentity}. We assume its the objectguid in Active Directory?
Hello Qasim,
thanks for the clearification!! The next question would be, why it fails with “File or directory not found” when we make the call.
We try it like this:
…/GroupIDDataService/api/IdentityStores/2/Users/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
Where 2 is our IdentityStoreID and aaaaa… is the objectguid from our AD.
I am assuming that you were able to generate a bearer token first as well as confirmed that it is not expired. Moreover, can you please confirm the following:
Which version of GroupID are you currently on?
Are you using GET method to execute this call?
Syntax that you shared is correct, so I would like to know the other details that are related to this API Call.
Hello Quasim,
sorry for the late reply, work got in my way
We are on Version 11.1.25134.03
We are using Postman to accomplish this, here we can authenticate as documented and receive a bearer token from the api. We use this in Postman to authenticate and use a get method to receive the described information.
After your last post I tried to authenticate with garbage in the bearer token authentication and the result was the same. So I’m currently suspecting that postman is not correctly delivering the bearer token. I’ll try other ways to deliver the token and post my progress here.
we made sure we use a get request but it doesn’t work.
We have the following setup:
We sucessfully post https://Server:4443/GroupIDSecurityService/connect/token with username and password of a read only user (from AD) to get a token. Here we get delivered the access_token which we then use in our get request:
Thank you so much for the detailed response. It does not appear to be authorization issue as it would give you a “401-Unauthorized” error.
Allow me to review this and I will get back to you shortly. This appears to be a server error that it is trying to communicate with. However, I would like to do some testing at my end regarding this.
It’s working in my environment. It might be easier to open a support ticket via our Technical Support portal, so we can look at your environment specifically.