Hello guys!
I’m writing in reference to the SAML authentication in Appian. I’ve trying to set it up on our environment using a ADFS from Microsoft. I am having some trouble to make it work; all the configuration is apparently well done in Appian, I have the metadata and the certificate. When I try to sing in, Appian takes me successfully to the sing in page of the ADFS, however there’s an error that stops me from going further. I’ve double checked the configuration from the ADFS trying to see if there is some missing parameters or configuration but there’s no success either.
I am posting some screens of my configuration in Appian and the error I’m getting while trying to sign in, hoping there’s something to do or to see if there’s any advice you could give me. Thanks in advance!!
The error:
My configuration in Appian:
Thanks again!
Discussion posts and replies are publicly visible
Hi Samuel Torrero (samuelt0001) , I hope "Service Provider Identity Id" i.e "testingitdemo" you have shared with your SSO team (those who gave you Identity Provider Metadata). Please check this. While generating .pem file you have mentioned some password, make sure you are useing same password here as well "Service Provider Signing Certificate Password". Please check above mentioned 2 points only. Thanks, Sandeep
Hi Sandeep,
Thanks for your help again! We have moved a few things and now I can go through the sing in page of the ADFS. The error now is that when I type in my credentials it returns to Appian with this error:
In the ADFS I can also see the following error:
(I hope the image is not too small, I could't find a way to make it larger)
That's were I am stuck now, any advice?
Thanks a lot again!
Samuel Torrero
Hi Sandeep Deshmukh
I've updated the .pem certificate and I'm doing everything now in Chrome. The error in Appian remains the same, however the error in ADFS has changed. It appears that the authentication method is not recognized by ADFS. I've tried using several ones in Appian, including the "unspecified" one but I'm getting the same error.
Here's the screen:
Thank you very much again!!