URI became invalid

  • Dear,
    I have been using AuthLdap for almost 1 year and half and all was working fine. This weekend, it stopped working. Error:
    ldap://cn=auth.ldap,ou=Service_Accounts,ou=ITS,ou=Admin,ou=Security,ou=Staff,ou=GUtech_Sec_Dist_Groups,dc=gutech,dc=edu,dc=om:123qqq!@#@172.16.2.11/dc=gutech,dc=edu,dc=om seems not to be a valid URI
    I upgraded to latest version of AuthLDAP but same error. I did not change anything in the server or the website or the AD. It really came suddenly. Any clue please?

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author heiglandreas

    (@heiglandreas)

    Hey there.

    Sorry to hear that the plugin suddenly stopped working. Or was that after an update? One of the last updates introduced URL-encoding the password to allow better usage of characters that are reserved for URLs. That includes f.e. ‘@’ and ‘#’ as they are special characters within an URL.

    If you have such characters in the password or the Bind-DN you’ll now need to URL-encode them. You can use an online-encoder like https://www.url-encode-decode.com f.e.

    After replacing the offending characters with the url-eroded ones everything should work as before.

    If not please get in touch with me ASAP so I can help you solve the issue! (feel free to ping me via authldap AT heigl DOT org)

Viewing 1 replies (of 1 total)
  • The topic ‘URI became invalid’ is closed to new replies.