By: yousif nakkash user 25 Dec 2020 at noon CST

5 Responses
yousif nakkash gravatar
I just configured LDAP and the cach refresh and set the default login to use LDAP instead of simple password and I am getting error"An unexpected error has occurred at null" . Is there a way to set the default login back to simple password. It doesnt make sense each time there is an issue with the server I have to reploy and go over all the settings again.

By Jose Gonzalez staff 25 Dec 2020 at 2:08 p.m. CST

Jose Gonzalez gravatar
Hi yousif, Please check https://www.gluu.org/docs/gluu-server/operation/faq/#revert-an-authentication-method

By yousif nakkash user 25 Dec 2020 at 9:14 p.m. CST

yousif nakkash gravatar
Can you please outline the steps to revert to the default method. apparently the steps above doesnt work. I created the ldif file and I am running the command and its giving me the error below: ``` [root@cas ~]# ldapmodify -h localhost -p 1636 -D "cn=directory manager" -w "password" -f changeAuth.ldif The LDAP bind request failed: 91 (Connect Error) Additional Information: Connection refused ``` I relaced the word password with the password I chose during the installation

By Mohib Zico Account Admin 26 Dec 2020 at 6:09 a.m. CST

Mohib Zico gravatar
It just required simple [adjustment](https://github.com/GluuFederation/docs-gluu-server-prod/commit/fe3c2378673a07e300d0ebe1c64f9a1277732d04). ``` [ldap@test42final ~]$ /opt/opendj/bin/ldapmodify -h localhost -p 1636 -D "cn=directory manager" -j /tmp/.pw -f changeAuth.ldif The LDAP bind request failed: 81 (Server Connection Closed) [ldap@test42final ~]$ /opt/opendj/bin/ldapmodify -h localhost -p 1636 -Z -X -D "cn=directory manager" -j /tmp/.pw -f changeAuth.ldif Processing MODIFY request for ou=configuration,o=gluu MODIFY operation successful for DN ou=configuration,o=gluu [ldap@test42final ~]$ ```

By yousif nakkash user 26 Dec 2020 at 9:08 a.m. CST

yousif nakkash gravatar
Thank you for your help. I was able to run the script successfully but still its giving me the error" An unexpected error has occurred at null". which logs show you what the problem is and how to fix it? is there a way to set the logs to debug from the cli?

By Mohib Zico Account Admin 26 Dec 2020 at 9:55 p.m. CST

Mohib Zico gravatar
Hi Yousif, Please allow me to help you how you can use "community support" in Gluu. - "Community Support" is not "specialized support", that means... this support is for "whole community". When we answer some community ticket, that means it has to serve purpose to whole community. "Specialized Support" is for "VIP customers". - "Community Support" ticket is not private tickets because whole community is able to search any problem in this support portal and take benefit from those if they face similar problem. - You have to know "what" you are doing and "how" you are gonna do it with Gluu Server. That means you have to read our documentation carefully and move forward. - After following all steps above, if you still face problem... you can definitely open ticket. But, you have to follow [How to Ask Good question](https://support.gluu.org/docs/user-guide/how-to-ask/) in support portal. Now.. to answer your question.... >> I was able to run the script successfully but still its giving me the error" An unexpected error has occurred at null". which logs show you what the problem is and how to fix it? If you just search our support portal with this error message, you would get a very good amount of community / public tickets on that specific problem. Screenshot attached.