question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WMS authentification problem with LDAP

See original GitHub issue

I have a problem with WMS service with login/password. I tried to use wms link with qgis with login/password. The message error is : L'hôte requiert une authentification... It doesn’t recongize my login. Without login, it work… I have lizmap 3.1.0 and qgis serveur 2.14 I have ldap configuration. The problem has been detected since we change lizmap version (3.0 before ), qgis version (2.8 before) and authentification type (was normal before). We tried to edit the virtualhost with :

RewriteEngine on
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

But it doesn’t work… Any solution? Thank you.


J’ai un problème avec le service WMS avec login/mot de passe. J’ai tenté d’utiliser le lien wms sur qgis avec mon login et mon mot de passe. Le message d’erreur est : L'hôte requiert une authentification... Il ne reconnait visiblement pas mon login. Pourtant, avec un lien WMS qui ne nécessite pas d’authentification, cela fonctionne… Je dispose de lizmap 3.1.0 et qgis serveur 2.14 Lizmap utilise une authentifcation ldap dans le paramétrage le problème est survenue depuis le changement de type d’authentification (normal), de version lizmap (3.0) et de version qgis (2.8). Nous avons tenté de modifier le virtualhost avec les lignes suivantes :

RewriteEngine on
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L]

ça n’a pas marché… Une idée? Merci d’avance pour votre aide

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
Gustrycommented, Aug 30, 2018

@rldhont As a tip, in my own repo, I’m using a label “Candidate for closing”, so a few weeks later, I can loop in this list and I know that I can safely close this issue if no more feedbacks are coming. My 2 cents 😉

0reactions
rldhontcommented, Nov 23, 2018

I close it, reopen if needed

Read more comments on GitHub >

github_iconTop Results From Across the Web

Why am I receiving the message "We cannot reach your ...
Resolution. A WMS site using LDAP as their authentication method has changed or updated their LDAP server domain and/or port number.
Read more >
LDAP configuration error in Geoserver - GIS Stack Exchange
Now I am trying to establish Geoserver authentication provider using LDAP as setting shown below: I think there is a problem with server...
Read more >
LDAP: error code 8 - 00002028: LdapErr: DSID-0C090259 for ...
The error seen is caused when LDAP server is configured to require signed communication, simple bind requests (through port 389 for example) are ......
Read more >
WMS Dispatcher Integration with Active Directory (LDAP)
Dispatcher password authentication will be performed against the WMS database if the user is not a LDAP user. If the user is a...
Read more >
Dell Wyse Management Suite Version 3.2 Administrator's ...
wyse-wms | Dell Wyse Management Suite Version 3.2 Administrator's Guide ... If you connect using LDAP port 389, a warning message is displayed...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found