Marco Telescope Live

How can I access the ticket? I haven't received any email about it. Thanks

Hi Marc, Just a follow-up on this. We will launch the forum over the next few days, and we need the Sign In to our own Login page. What is the update from the development team? Thank you!

After the user is redirected to our site and gives their credentials there, we redirect them back to Invision Community while using the callback given to us when registering the OAuth2.0 client: The Redirect URI to use is https://{ourId}.invisionservice.com/oauth/callback/ Then we get the mentioned error above.

Hi Marc, right now we are using OAuth 2.0 with Authorization code flow and the issue we are experiencing is when we redirect the user back to Invision Community after they have provided their credential on our Login & Registration section. Apologies, for not pointing that out earlier. Kind regards

Hi everyone, We are currently integrating our custom Identity Provider service into an Invision Community. We have already registered and added a login client inside the "Login & Registration Methods" tab. We are using the Authorization Code flow to redirect our users on Sign In to our own Login page where they enter their credentials. After a successful login, they are redirected back to Invision Community with a valid authorization code added to the response including the state fields. Right after we are redirected back to Invision Community with the provided callback with auth code and state fields - "Redirect URI?code&state", we are getting an error "Something went wrong. Please try again." and the user is not being logged in. Although we have checked the Error Logs in the admin panel, we did not manage to find exactly why we are getting this error. There are a few more exception messages on the Log, e.x.: 2C122/1 The page you are trying to access is not available to guests, but may be available if you sign in. 2S119/1 The CSRF protection key did not match. This may indicate a plugin or theme is out of date. Please contact technical support for more information. Is there anything we can do to get more info on why exactly we are getting this error when we are redirecting back the user to Invision Community? Kind regards