-
Notifications
You must be signed in to change notification settings - Fork 570
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
PingOne / Ping Desktop errors with "Unknown document type" #717
Comments
I had the same issue but with Ping. |
Hey @ckabalan |
Also facing the same issue unfortunately. |
Hi @ckabalan, did you find the solution for this? I am facing the same issue. |
@Prakash-HPE and @OSobky: I have moved on to a different company (AWS actually), but never did find a solution. Our organization ended up moving to AWS Single Sign-On (IAM Identity Center), which was of course a conversation with the identity team, yada yada... |
This works for me. I deleted one device and it's now connected. |
I am attempting to configure
saml2aws
with a brand new deployment of PingOne / Ping Desktop and PingFederate backend. I'm getting anUnknown document type
error, which I believe is the result of a different page/redirect structure thansaml2aws
is looking for.My configuration:
Debug output:
I played around with the code and got this to be detected as a resume or redirect page. It moved further through the process and proceeded to a new page at
https://desktop.pingone.com/mycompany/Selection?cmd=selection
with some interesting variables likeppmRequest
andppmResponse
. I believe this is our organization's dashboard page because shortly after this page is loaded in a browser via a normal login process it hits a URL ending in/apps
which returns JSON related to the tiles on the Ping Desktop, which includes the redirect URL to PingFederate. I have no idea how to fill the gap between the Selection page and getting to the AWS redirect with SAML.Any ideas? Am I the only one having this issue? Has the PingOne functionality been abandoned and no longer works with a new portal? Are we using a more modern portal from the rest of the customers and only we're broken?
Any insight would be helpful. I'm not a golang developer but I'm willing to try to do what I can and collaborate with any developers that want to help resolve this.
Thank you for your time.
The text was updated successfully, but these errors were encountered: