Challenge Overview
In recent challenges Cloud Hub has built the capability to allow users to use SAML to login with third party identity managers. We need to allow the customer to save the SAML settings against their company to use on for the integration.
Requirements
1. Create /saml page inside web app to allow storage of SAML fields:
a. Status (dropdown Off / Okta, company.sso_provider)
2. SAML SSO URL
3. Identity Provider Issuer
4. Public Certificate
2. Update API & swagger to store this information in a new JSONB field called saml. This should replace sso_provider.
3. Update app-saml.js to use data for strategies inside database and remove fields in ssoConfig.
4. Update oktaSAML.js file in seeds to set the strategy.
SAML database sample
{
"sso": "okta",
"okta": {
"entry": "https://dev-961511.oktapreview.com/app/highalphadev961511_zylo_1/exk6l62vnpw3XQKt30h7/sso/saml",
"issuer": "http://www.okta.com/exk6l62vnpw3XQKt30h7",
"cert": "{{cert}}"
}
}
Requirements
1. Create /saml page inside web app to allow storage of SAML fields:
a. Status (dropdown Off / Okta, company.sso_provider)
2. SAML SSO URL
3. Identity Provider Issuer
4. Public Certificate
2. Update API & swagger to store this information in a new JSONB field called saml. This should replace sso_provider.
3. Update app-saml.js to use data for strategies inside database and remove fields in ssoConfig.
4. Update oktaSAML.js file in seeds to set the strategy.
SAML database sample
{
"sso": "okta",
"okta": {
"entry": "https://dev-961511.oktapreview.com/app/highalphadev961511_zylo_1/exk6l62vnpw3XQKt30h7/sso/saml",
"issuer": "http://www.okta.com/exk6l62vnpw3XQKt30h7",
"cert": "{{cert}}"
}
}
Sample page showing the fields we are going to be storing: http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Slack.html
Final Submission Guidelines
1. Any additions or modifications to the code project pass on "npm run lint" and "npm run test".2. Provide your code and documentation in a single zip file. Please include a git patch for easier integration of changes.
3. The bulk of your documentation should be in the Readme.md and you should assume that this will be open source so make sure you cover all the steps to set up, If you have specific information that should not be included in a public readme (like links to your video) put them in a file called submission.txt and they will be omitted from the project if it is open sourced.
4. Provide a quick video of your solution in action (feel free to annotate your video if you are not comfortable with spoken English or don’t like the sound of your own voice). Video may be private on youtube or added to the submission files. Your video can skip the setup of your environment, linting and tests. We are interested to see the new functionality of the app in the video.