What happened?
When configuring wanderer with OpenStreetMap (OSM) as an OIDC provider, newly created users receive a numeric ID as their username instead of their OSM display name.
Without a scope override, OSM login fails outright; with one, it succeeds but the username is discarded.
Root causes:
- PocketBase's default OIDC scopes include email and profile, which OSM rejects. wanderer needs a way to override these scopes per deployment.
- Even with correct scopes (
openid read_prefs), OSM returns preferred_username but PocketBase's internal oldCanAssignUsername check silently fails, causing username assignment to be skipped and a numeric fallback to be used.
Version
v0.19.1, v0.20.0, dev
Why you should add OSM auth
Your tool is based on OSM data, and a lot of the auth providers you offer here are typical big tech players that, especially OSM people do not use by default 😂
Even new users could get a recommendation to create an OSM account. By going this way, the chance is higher to get people hooked into the OSM world. A lot of services can use the OSM account.
What happened?
When configuring wanderer with OpenStreetMap (OSM) as an OIDC provider, newly created users receive a numeric ID as their username instead of their OSM display name.
Without a scope override, OSM login fails outright; with one, it succeeds but the username is discarded.
Root causes:
openid read_prefs), OSM returnspreferred_usernamebut PocketBase's internaloldCanAssignUsernamecheck silently fails, causing username assignment to be skipped and a numeric fallback to be used.Version
v0.19.1,v0.20.0,devWhy you should add OSM auth
Your tool is based on OSM data, and a lot of the auth providers you offer here are typical big tech players that, especially OSM people do not use by default 😂
Even new users could get a recommendation to create an OSM account. By going this way, the chance is higher to get people hooked into the OSM world. A lot of services can use the OSM account.