What I'm still missing is how to get the saml2 assertion.
The following articles try to explain it and I've red them carefully but I don't understand "who" to call first to get a SAML assertion. Which address should I use?
The SAML OAuth flow begins when your app redirects the user to the 3rd party auth provider. In the case of the example app, this is done here.
Next, the 3rd party auth provider will perform any necessary steps to authenticate the user. Once the user has been authenticated, the auth provider will make a POST request to the URL you've configured with the auth provider to send the SAML assertion. In the case of the example app, this is recieved here. When you receive the assertion, you can then use it to request an auth token from PureCloud.
That's a URL for my Okta instance, so it isn't going to do you any good anywhere. I don't have any experience configuring ADFS, so I can't advise you how to set up your instance except to follow the documentation.
I understood the example is for another identity provider. I was just trying to do the "mapping" to ADFS. On the ADFS side the only url that was configured is the one on the documentation: https://login.mypurecloud.ie/saml
Are u aware of some colleague of urs, that might have been somehow involved in a ADFS integration and that could help us? We are kind of stuck here
I've asked around, but we don't have any in-house ADFS experts. Microsoft does have documentation on configuring the ADFS server though. This article may be relevant to you: https://technet.microsoft.com/en-us/library/gg188595.aspx
Allow me to get back on this subject. We manage to perform authentication trough ADFS using PureCloud's front end. This means that both ADFS and PureCloud Organization are correctly configured. We now want to replicate this mechanism in our custom front-end using the REST API. We were wondering if our front-end application also needs to be a Relying Party in ADFS, does it?
