Additional Info:
In the previous stable version v2.8.9, on domain.com/invites/invitecode :
-
A non-logged in user would be presented with a screen that asks them to login via SSO (Okta which is specified in the app.yml SAML config), which will redirect them to SSO to login/register, afterwards it will execute the invite actions (redirect to topic, add to group, etc)
-
A logged in user would automatically bypass the invite screen and the invite actions will be executed
In the current stable version v2.8.10, on domain.com/invites/invitecode :
- Both non-logged in and logged-in users will be presented with the invite screen with 2 buttons:
– Login via SSO Button
– Accept Invitation (this is new)
When the Login via SSO button is clicked, the user is prompted to login (if not logged in) and will be redirected back to the invite page again.
When the Accept Invitation button is clicked, nothing happens.
We observed in the network browser console that there is a PUT request to domain.com/invites/show/invitecode.json which is returning a 504 error (only in the 2.8.10 version)