A user, aboutDavid, reported that adding an OpenID Connect provider with a .ong domain (e.g., obl.ong) fails because Discourse treats .ong as an “internal hostname”—a behavior that can be worked around by modifying site settings. The issue appears tied to Discourse’s auto-linking of .ong domains, which hello-smile6 suggests may be a plugin or custom configuration issue, noting that such behavior was manually configured on AMC rather than being default. aboutDavid expressed frustration over the need to frequently adjust settings. In a tangent, Jagster asked about the meaning of .ong, to which Moin replied that .ong is a top-level domain intended for non-governmental organizations, derived from “organisation non gouvernementale” in French and similar terms in other Romance languages. The bug is tagged under OpenID Connect and relates to hostname validation logic in Discourse.
Hello, I was trying to add obl.ong as an openid connect provider, but apparently .ong domains are seen as a “internal hostname”. Adding it there fixed it but this seems like a bug.
Versions:
OpenID Connect 1.0 (Update translations (#73) · discourse/discourse-openid-connect@f31a869 · GitHub)
Discourse 3.3.0-beta1-dev (Commits · discourse/discourse · GitHub)
That seems to be something manually configured on AMC, rather than the default.
Ah I see. Why do we have to change so many settings so often :nooooooooo:
Very off topic and perhaps very stupid question too, but what .ong should describe, what is its meaning?
The PIR simultaneously applied for the top-level domain .ong, which is a similarly recognisable initialism for “organisation non gouvernementale” in French, and equivalent terms in many other Romance languages such as Spanish, Portuguese, Italian and Romanian.
