Match score not available

Cloud Engineer - DI - Identity Access

Remote:

Full Remote

Contract:

Freelance

Experience:

Mid-level (2-5 years)

Work from:

Brazil

Offer summary

Qualifications:

Proficient in Azure B2C and Okta, Experience with identity management systems, Strong understanding of user migration processes.

Key responsabilities:

Analyze current authentication mechanisms.
Design user migration strategies to Okta.
Conduct workshops on authentication flows.
Create registration and management requirements.
Document architecture and user flow diagrams.

AM53 Smart Solutions Startup https://www.am53.com.br/

11 - 50 Employees

See more AM53 Smart Solutions offers

Job description

Your missions

1. Assessment

Review current solution, goals, and challenges with core team.

· Perform a thorough analysis of the current authentication and authorization mechanisms for the Azure B2C, Ping Federate and Ex-Partner/Padum apps.

· Review existing process for user management (create, read, update and delete) within Azure B2C, Ping Federate and Ex-Partner/Padum applications for internal and external users.

· Understand any key issues likely to be raised by key stakeholder groups for supporting

Discuss future state requirements for authentication, authorization and user management within the applications.

2. User Migration Design

Conduct user migration workshop consisting of the following topics

· Review migration options that support migrating external users from Azure B2C, Ping Federate and Ex-Partner/Padum to Okta.

· Review how best to communicate user migration

· Review how user passwords will be managed (migrated or reset)

· Review how to handle duplicate accounts

· Review how to execute user migration (phased or big bang)

Review above options for both Okta CIS and CIC.

3. Authentication Flow and Integration Design

Conduct user authentication and authorization workshop consisting of the following topics

· Review options for integrating Okta authentication flows within the targeted applications

· Review authorization requirements for applications and review options in Okta to support.

· Review options for ensuring internal users will maintain access to applications federated with Okta.

· Review options for allowing external users to authenticate using either an external IdP or Social Network IdP.

· Review above options for both Okta CIS and CIC.

4. User Registration and Management Requirements Design

Conduct a user registration and management workshop consisting of the following topics

Review options for supporting self-service user registration flows for external users
Review requirements for supporting any admin approval functionality
Review initial sets of attributes required as part of the registration process
Review options for on-going user management
Determine the best path forward to build out the desired self-service registration flows and user management functionality within the environment.
Out of the box options
Customized solution
Review above options for both Okta CIS and CIC.

5. Project Documentation

Provide the following artifacts

Okta Architecture

a. This document will provide architectural information detailing the design to support the Clients desired migration, authentication, authorization and user management use cases for applications migrating from Azure B2C, Ping Federate and Ex-Partner/Padum to Okta. This will also provide details on the recommended Okta platform that will best meet the requirements (Okta CIS or CIC).

User Flow Diagrams

a. Migrations Flows

b. Authentication flows

c. Registration Flows

d. User Management Flows