#2078 closed task (fixed)
osgeo id login troubles reported via email
| Reported by: | jive | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Website rebranding 2017 |
| Component: | SysAdmin | Keywords: | ldap |
| Cc: |
Description
Going to start a general ticket here since emails are coming in:
- Maxi71 reports being unable to login to the new website, credentials worked with previous
- Ben Caradoc-Davies reports being unable to change his email address (it has his old work email address listed)
Change History (12)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Sent email, I guess without an osgeo_id they cannot comment on this ticket.
What is staging2 ?
comment:3 by , 6 years ago
jive staging2 is our PHP7/MariaDb test instance. staging is running PHP5/MySQL
I'll look into the issue with these two.
comment:4 by , 6 years ago
I responded to Ben.
I also changed the default for new users to Editor (instead of Subscriber).
Hopefully this will resolve most of the issues and then we can revise permissions later if needed.
follow-up: 8 comment:5 by , 6 years ago
Who is Maxi71? I don't see a wordpress login or LDAP account for such a person
comment:6 by , 6 years ago
I think email should be updated via https://id.osgeo.org/ldap/edit and a link to that page should be added from wordpress if it has any other "edit profile" page.
comment:7 by , 6 years ago
Staging2 is https://staging2.www.osgeo.org
Maxi71 is indeed unknown by LDAP: https://id.osgeo.org/ldap/search?query=maxi71
comment:8 by , 6 years ago
Replying to robe:
Who is Maxi71? I don't see a wordpress login or LDAP account for such a person
It's this Wiki account name: http://wiki.osgeo.org/wiki/User:Maxi71
comment:9 by , 6 years ago
How's the OSGeo sysadmin contract going ? We want to fix this extenuating WIKI accounts discrepancy :/
comment:10 by , 6 years ago
I tested the mail change ... First I got:
Your email address has not been updated yet. Please check your inbox at <my mail here> for a confirmation email. After a minute or so I received the confirmation mail.
And the change was done successfully
comment:11 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I'm assuming last comment means we can close this. Please reopen if I got it wrong.
comment:12 by , 8 months ago
IMHO this ticket has two aspects: The repository setup itself that external request might not be logged on osgeo instance AND the recommend setup on the repository manager that proxy osger repositories.
As written here its possible to define routing rules : https://help.sonatype.com/repomanager3/using-nexus-repository/repository-manager-concepts/proxy-repository-concepts#ProxyRepositoryConcepts-RoutingRules
I will try this on my end. nevertheless, why are these "wrong" requests lead to zero size artefacts in osgeo release repository? Is it a Nexus bug?
Can they test on staging2, please.