-
ratheeshvnair replied to the topic OpenDJ REST is not able to GET resources with special characters in UID(eg: +) in the forum Directory Services 6 years, 9 months ago
Thanks Ian & Ludo,
It was indeed my client. Works for me now. Really appreciate your help. -
ratheeshvnair replied to the topic OpenDJ REST is not able to GET resources with special characters in UID(eg: +) in the forum Directory Services 6 years, 9 months ago
Hi Ian,
Thank you very much for your reply. When I tried with encoded URL, in OpenDJ logs, I see the request being made as/users/abc%252Bxyz%2540test.com. I think it encoded % in %2B to %25. Is that happening within OpenDJ? Is there a way to tell OpenDJ not to do the double encoding?
Thanks
Ratheesh -
ratheeshvnair started the topic OpenDJ REST is not able to GET resources with special characters in UID(eg: +) in the forum Directory Services 6 years, 9 months ago
When I use OpenDJ REST end point to GET a user, It returns 404 if the user that I’m requesting has + in the uid.
REST is enabled using http connection handlers.
Eg : GET /users/[email protected], The response received is
{
“reason”: “Not Found”,
“message”: “No Such Entry: The search base entry ‘uid=abc…[Read more] -
ratheeshvnair started the topic OpenDJ REST is not able to GET resources with special characters in UID(eg: +) in the forum Directory Services 6 years, 9 months ago
When I use OpenDJ REST end point to GET a user, It returns 404 if the user that I’m requesting has + in the uid.
REST is enabled using http connection handlers.
Eg : GET /users/[email protected], The response received is
{
“reason”: “Not Found”,
“message”: “No Such Entry: The search base entry ‘uid=abc…[Read more] -
ratheeshvnair replied to the topic OpenDJ REST end point fail to update RDN in the forum Directory Services 7 years ago
Hi Ludo,
Thank you for your comments. Is there another way to get the entry updated(may be using LDAP SDK) outside of REST API’s?Thanks
-
ratheeshvnair started the topic OpenDJ REST end point fail to update RDN in the forum Directory Services 7 years ago
I’m using OpenDJ 2.6.0 and enabled http connection handler using the default configurations available in http-config.json file. When using OpenDJ REST to update user, it fails with the following message when update includes changing uid.
{“code”:400,”reason”:”Bad Request”,”message”:”Not Allowed on RDN: Entry…[Read more]
-
ratheeshvnair started the topic OpenDJ REST end point fail to update RDN in the forum Directory Services 7 years ago
I’m using OpenDJ 2.6.0 and enabled http connection handler using the default configurations available in http-config.json file. When using OpenDJ REST to update user, it fails with the following message when update includes changing uid.
{“code”:400,”reason”:”Bad Request”,”message”:”Not Allowed on RDN: Entry…[Read more]
-
ratheeshvnair replied to the topic OpenAM json/authenticate password failure update pwdFailedTime field twice in DJ in the forum Access Management 7 years, 6 months ago
Hi Peter,
I forgot to update the forum earlier. I was able to solve the problem. I had to configure the LDAP authentication module pointing to the DJ server and then it started working.Thank you for your reply.
Regards
Ratheesh -
ratheeshvnair started the topic OpenAM json/authenticate password failure update pwdFailedTime field twice in DJ in the forum Access Management 7 years, 6 months ago
I have OpenAM 12.0 connecting to external OpenDJ 2.6.0 for identity data. I have configured the account lockout in OpenDJ to lock the user after 5 failed authentication attempt. But I noticed that when the OpenAM authentication REST api(json/authenticate) makes the call and if the authentication fails with incorrect password, it creates two…[Read more]
-
ratheeshvnair started the topic OpenAM json/authenticate password failure update pwdFailedTime field twice in DJ in the forum Access Management 7 years, 6 months ago
I have OpenAM 12.0 connecting to external OpenDJ 2.6.0 for identity data. I have configured the account lockout in OpenDJ to lock the user after 5 failed authentication attempt. But I noticed that when the OpenAM authentication REST api(json/authenticate) makes the call and if the authentication fails with incorrect password, it creates two…[Read more]
-
ratheeshvnair started the topic OpenAM json/authenticate password failure update pwdFailedTime field twice in DJ in the forum Access Management 7 years, 6 months ago
I have OpenAM 12.0 connecting to external OpenDJ 2.6.0 for identity data. I have configured the account lockout in OpenDJ to lock the user after 5 failed authentication attempt. But I noticed that when the OpenAM authentication REST api(json/authenticate) makes the call and if the authentication fails with incorrect password, it creates two…[Read more]
-
ratheeshvnair started the topic OpenAM json/authenticate password failure update pwdFailedTime field twice in DJ in the forum Access Management 7 years, 6 months ago
I have OpenAM 12.0 connecting to external OpenDJ 2.6.0 for identity data. I have configured the account lockout in OpenDJ to lock the user after 5 failed authentication attempt. But I noticed that when the OpenAM authentication REST api makes the call and if the authentication fails with incorrect password, it creates two pwdFailureTime record in…[Read more]