-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSO Integration Issue #192
Comments
When you input the SSO IdP into VECTR it will generate a list of URLs, these URLs should be put into the SSO entry under the IdP platform(Azure). I'll leave this open but we don't usually offer community support for SSO, see the guidelines. |
Hi @SRAPSpencer. Yes, I put those list of URLs into SSO in Azure platform but still won't work? I get the that error. |
The error means that you didn't specify the VECTR callback URL in AAD. Can you double check this. The VECTR callback URL is If you've setup an OIDC application, the callback URL in AAD is the "Redirect URI": If you've setup a SAML2 application, the callback URL in AAD is the "Reply URL (ACS)": |
Yes, I followed those steps as well but didn't work. |
Unfortunately we cannot provide SSO onboarding support to the open community as configuration of SSO with the identity / SSO provider is highly variable as well as differences in organizational level security policies and procedures that can impact how SSO is configured. If you're not already on our Discord channel, I would recommend joining and asking the community for help. https://discord.gg/2FRd8zf728 |
Hi Team,
I am having issue with integration VECTR into SSO. The error is "No Reply address was provided". Although, I provided the Reply Address. I tried both AzureAD and SAML but wouldn't work.
Any recommendation, please?
![VECTR_Issue](https://user-images.githubusercontent.com/33989965/190662344-1eb3c25b-f9d5-496b-9a6c-c81d268fb35d.png)
The text was updated successfully, but these errors were encountered: