Started to implement SSO for one of my project without knowing anything.
Trying to note down to identify the bits and pieces here.
Steps followed :
When sending Authentication request pass the RelayState parameter as below :
On AssertionConsumerServiceUrl check for the RelayState url parameter is passed back :
Issues I will be working on next are :
1. Registration - how it works from custom website
2. How it will works for manual approval for registered users.Any api or else ?
3. How the authentication works through this custom site wide - do I need to ping every time to Idp ?
Ultimate goal is to prepare a project template that can be reused.
Trying to note down to identify the bits and pieces here.
Steps followed :
- Set up a dev account with Salesforce. https://developer.salesforce.com/signup
- Playing with Salesforce how SAML based authentication works in there : https://developer.salesforce.com/docs/atlas.en-us.identityImplGuide.meta/identityImplGuide/identity_quickstart_SAMLgen.htm
- Set up a custom web application (SP-service provider) to work with Salesforce (Idp) : https://developer.salesforce.com/page/Configuring-SAML-SSO-to-Custom-.Net-Application
- Step 4 din cover how I can actually redirect to a particular page after successful login. Utilising the RelayState parameter.
When sending Authentication request pass the RelayState parameter as below :
Issues I will be working on next are :
1. Registration - how it works from custom website
2. How it will works for manual approval for registered users.Any api or else ?
3. How the authentication works through this custom site wide - do I need to ping every time to Idp ?
Ultimate goal is to prepare a project template that can be reused.
