0

So, I have an angular web app that our org wants to integrate with PingIdentity and SSO. The 2LDR Problem is, we have HashRouting set on our application, and PingIdentity will not accept an ACL (redirect_url) with a hash in it.

For more context, in order to make it so that you can... you know, refresh the page and not get a 404, we had to set HashLocationStrategy in the app.module in our web app (which is hosted in Azure). I've set up a controller to accept the Ping auth response (https://myapp.domain.com/#/auth/callback). However, our security admin is telling me that they can not set this URL because it has a hash in it. The error they're getting in their Ping admin console is "Fragment component is not allowed."

Has anyone implemented Ping with an Angular app with HashRouting or have any idea of a good workaround? I suppose I could just give them the root url (https://myapp.domain.com/) and then handle it in app.component, but... I'm really looking for a better option where I can use the controller I've set up.

Thanks so much!

Improve this question
1
  • nothing past the "#" would be sent to your server anyway, so I think you'd want a redirectURL that would hit your server and not the single page... (since that redirect URL would need to have an access id or something like that which would need to be processed... I think that bit is server-to-server... then it can set cookies and redirect back to your single page.) Commented Jun 6 at 16:33
Related questions
1247
Angular: conditional class with *ngClass
947
ngFor with index as value in attribute
32
Keycloak - direct user link registration
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.