Discourse does not allow group starting or ending by dot [.]

[warlof]

It appears that the login flow is currently sanitize the role name but keeping leading and ending dot [.] character.

As a result, the user will get all group except those containing a dot at the beginning or ending position.

Not working case :
..TICKER
TICKER.

Working case :
TI.CKER

[herpaderpaldent]

Could you give me a little more information on this issue? I would need to know what is been created on Discourse and what is synced.

SeAt	Discourse	Working?
..Ticker	?	No
Ticker.	?	No
TI.CKER	TI.CKER	YES

All i do is using the studly_case() Method and i am surprised that the dot [.] sanitized.
https://github.com/herpaderpaldent/seat-discourse/blob/master/src/Action/Discourse/Groups/Attach.php#L33

If the error lies here, the dot is missing in the groups name in Discourse.

However it might be an error in the SSO-Provider:
https://github.com/herpaderpaldent/seat-discourse/blob/master/src/Action/Discourse/Groups/Attach.php#L33

[warlof]

Let's take a character with the following roles :

• TICKER.
• ..TICKER
• TICKER.LEADERSHIP

When this user will auth to Discourse, he will get TICKER.LEADERSHIP only
Update .TICKER to TICKER, and on next sign in, he will get TICKER.LEADERSHIP and TICKER - but still not ..TICKER

[herpaderpaldent]

from the code pov i don't really see why this is happening.

Though ppl using dots as Rolenames is a special use case but ofc i should account for this. I'll look into it thank you :D