Authentication via LDAP does not work when going through the privacy policy screen #141
Labels
bug
Bug
development
Deployed to development environment
high priority
High priority
production
Deployed to production environment
staging
Deployed to staging environment
When a new user authenticates via LDAP and goes through the privacy policy, the final target is on the old form, which includes only the hostname, not a complete URL. It looks like this can be fixed by modifying the line in dataportal.properties:
auth.target=portal.edirepository.org
to
auth.target=https://portal.edirepository.org/nis/login
We will do this update during the maintenance window on Wednesday.
The text was updated successfully, but these errors were encountered: