Challenge Overview
Cloud Hub has an existing integration to pull in applications, users and events from an SSO provider. We have clarified our requirements and need to update the implementation. There was some confusion when we built this integration and there are a couple of jobs that run the integration. We want to simplify the integration and only have 1 job to run the process. We have broken down the process to each event with details.
Add Applications
1. Any applications found in Okta would be added with Status (A) and Source (Okta).
2. Any applications that don’t match our library are sent to unMatched email that already exists.
3. Existing logic that stores oktaId and uses that to match updates should stay the same.
Add Users
1. Existing logic to add/update users should stay the same, but password can be removed.
2. If mask is turned on store random UUID in user_name, do not store first_name, last_name or email.
3. The adding apps to users functionality can be removed.
Add Events
1. Existing functionality can stay the same.
General Requirements
1. New option with integration to mask data, if this is true in settings we don’t want to store user’s name or email.
2. Modify database logic that requires email and password for users.
3. Remove ability to roleType user to login to application. They should have no API rights at this time.
4. Create single job to run integration, remove the other 3 jobs.
5. Clean up tests for changes in logic.
Integration overview will be provided in forums for anyone not familiar with these challenges.
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.
Add Applications
1. Any applications found in Okta would be added with Status (A) and Source (Okta).
2. Any applications that don’t match our library are sent to unMatched email that already exists.
3. Existing logic that stores oktaId and uses that to match updates should stay the same.
Add Users
1. Existing logic to add/update users should stay the same, but password can be removed.
2. If mask is turned on store random UUID in user_name, do not store first_name, last_name or email.
3. The adding apps to users functionality can be removed.
Add Events
1. Existing functionality can stay the same.
General Requirements
1. New option with integration to mask data, if this is true in settings we don’t want to store user’s name or email.
2. Modify database logic that requires email and password for users.
3. Remove ability to roleType user to login to application. They should have no API rights at this time.
4. Create single job to run integration, remove the other 3 jobs.
5. Clean up tests for changes in logic.
Integration overview will be provided in forums for anyone not familiar with these challenges.
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.