<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sandeepan Dey on Medium]]></title>
        <description><![CDATA[Stories by Sandeepan Dey on Medium]]></description>
        <link>https://medium.com/@sandeepan-dey?source=rss-70c5aeb4ac58------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*seH4BV47yWesi6dZrUCR8g@2x.jpeg</url>
            <title>Stories by Sandeepan Dey on Medium</title>
            <link>https://medium.com/@sandeepan-dey?source=rss-70c5aeb4ac58------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 05:16:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sandeepan-dey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Implementing a PAM Solution in a Multi-Cloud Environment -A Technical Program Manager viewpoint]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://sandeepan-dey.medium.com/implementing-a-pam-solution-in-a-multi-cloud-environment-a-technical-program-manager-viewpoint-09706efe668f?source=rss-70c5aeb4ac58------2"><img src="https://cdn-images-1.medium.com/max/1400/0*BrujlRa63dzR8hoT.png" width="1400"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://sandeepan-dey.medium.com/implementing-a-pam-solution-in-a-multi-cloud-environment-a-technical-program-manager-viewpoint-09706efe668f?source=rss-70c5aeb4ac58------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://sandeepan-dey.medium.com/implementing-a-pam-solution-in-a-multi-cloud-environment-a-technical-program-manager-viewpoint-09706efe668f?source=rss-70c5aeb4ac58------2</link>
            <guid isPermaLink="false">https://medium.com/p/09706efe668f</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[delivery-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[multi-cloud-security]]></category>
            <dc:creator><![CDATA[Sandeepan Dey]]></dc:creator>
            <pubDate>Fri, 24 Jan 2025 00:54:58 GMT</pubDate>
            <atom:updated>2025-01-24T00:54:58.446Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Implementing Okta SSO in a Monolithic Java Application: A Tech Program Manager’s Journey]]></title>
            <link>https://sandeepan-dey.medium.com/implementing-okta-sso-in-a-monolithic-java-application-a-tech-program-managers-journey-e1f46c5707b6?source=rss-70c5aeb4ac58------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1f46c5707b6</guid>
            <category><![CDATA[okta]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[program-management]]></category>
            <dc:creator><![CDATA[Sandeepan Dey]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 19:37:56 GMT</pubDate>
            <atom:updated>2024-10-01T19:51:06.954Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_6I8DRQ8q0omAPLAXSM4ow.png" /></figure><p>In today’s rapidly evolving tech environment, security is paramount. For organizations moving towards Single Sign-On (SSO) solutions, Okta is a widely trusted identity management provider. As a Tech Program Manager overseeing a monolithic Java-based application, implementing Okta’s SSO solution was a crucial project — both technically and strategically. By applying <strong>PMI</strong> and <strong>Scrum</strong> principles, we managed to mitigate risks, stay within budget, and deliver a robust, secure authentication solution on time.</p><p>This article will walk you through the process we undertook to implement Okta SSO, exploring the different integration options and why we ultimately settled on using the <strong>Okta API</strong>. From initial risk assessments to final implementation, this was a complex but rewarding journey.</p><h3>1. Project Initiation: Setting the Groundwork</h3><p>The journey began with the need to enhance user security and improve the user experience by replacing the traditional username/password mechanism with an SSO solution. Okta was selected as the SSO provider due to its scalability, security features, and compatibility with the Java ecosystem.</p><h4>Initial Planning:</h4><p>As a tech program manager, I followed the <strong>PMI framework</strong> for the project initiation:</p><ul><li><strong>Define Objectives</strong>: Enable Okta-based SSO to streamline authentication.</li><li><strong>Scope</strong>: Integrate Okta SSO into our existing monolithic Java application without overhauling the entire authentication system.</li><li><strong>Stakeholder Engagement</strong>: Engaged with developers, cybersecurity experts, and key business stakeholders.</li><li><strong>Risk Identification</strong>: Potential challenges included integration complexity, impacts on existing users, and budget constraints.</li><li><strong>Customer Alignment :</strong> Two of our biggest clients with unique and conflicting needs had to be onboarded on the SSO and MFA solution.An early engagement model with both of them helped keep the project on track.</li></ul><p><strong>Deliverable</strong>: A project charter outlining goals, scope, timeline, and risks. By involving all stakeholders early on, we ensured that everyone was aligned from the start.</p><h3>2. Exploring Okta Integration Options</h3><p>The next step involved evaluating various integration methods for implementing Okta in a monolithic Java application. We focused on three primary options:</p><h4>Option 1: Okta SAML Integration</h4><p>Security Assertion Markup Language (SAML) is a standard protocol for exchanging authentication and authorization data. Using Okta’s SAML support seemed like an attractive choice for enabling SSO across applications.</p><ul><li><strong>Pros</strong>: Easy to implement, widely supported, and secure.</li><li><strong>Cons</strong>: Limited flexibility for customizing the user interface or integrating advanced workflows.</li><li><strong>Risk</strong>: Our monolithic application required deep customization, which would have made SAML less than ideal.</li></ul><h4>Option 2: OIDC (OpenID Connect) with OAuth 2.0</h4><p>OpenID Connect (OIDC) is built on top of OAuth 2.0 and allows clients to verify the identity of end-users based on the authentication performed by an authorization server.</p><ul><li><strong>Pros</strong>: Highly flexible, with support for modern web and mobile applications.</li><li><strong>Cons</strong>: More complex to set up and manage compared to SAML.</li><li><strong>Risk</strong>: Increased complexity might impact the timeline and stretch the budget if we were not cautious with development cycles.</li></ul><h4>Option 3: Okta API-Based Integration</h4><p>Finally, the Okta API provides full programmatic control over authentication, offering the most flexibility. This would allow us to build custom authentication flows and integrate deeply with our existing system.</p><ul><li><strong>Pros</strong>: Full control, custom workflows, and future-proofing the authentication process.</li><li><strong>Cons</strong>: Required deeper integration and more development effort.</li><li><strong>Risk</strong>: Potential for longer development cycles and increased QA time.</li></ul><h3>3. Decision-Making and Risk Mitigation</h3><p>After evaluating all three options with the team, we chose to implement <strong>Okta API-based integration</strong>. This option provided the flexibility to tailor the authentication flow to our business needs and integrate seamlessly into the Java-based monolithic architecture.</p><h4>Applying PMI Risk Management:</h4><ul><li><strong>Risk Identification</strong>: API-based integration posed risks such as longer development time and potential cost overruns.</li><li><strong>Risk Mitigation</strong>: To manage these risks, we allocated additional resources for QA and incorporated buffer time into the timeline. We also engaged with Okta support early on to prevent integration pitfalls.</li></ul><h4>Budget Management:</h4><p>By using the <strong>PMBOK® Guide’s</strong> cost estimation techniques, we conducted a thorough cost-benefit analysis to ensure that the additional development and QA costs were justified by the long-term benefits of the Okta API integration. We monitored the budget closely throughout the project using <strong>Earned Value Management (EVM)</strong> to ensure cost adherence.</p><h3>4. Executing with Scrum: Sprint Planning and Development</h3><p>Once we chose the Okta API, the project execution phase followed Scrum methodology.</p><h4>Key Scrum Practices:</h4><ul><li><strong>Sprint Planning</strong>: We broke down the implementation into manageable chunks — authentication flows, error handling, user session management, and security testing. Each sprint had clear goals.</li><li><strong>Daily Stand-ups</strong>: Regular check-ins kept the team aligned and allowed us to identify roadblocks early.</li><li><strong>Sprint Reviews &amp; Retrospectives</strong>: After each sprint, we reviewed the deliverables and gathered feedback from stakeholders to improve future sprints.</li></ul><p>The development team focused on:</p><ul><li><strong>Custom Authentication Flows</strong>: Using the Okta API, we developed customized user sign-in and sign-up flows to enhance user experience.</li><li><strong>Session Management</strong>: We integrated Okta’s token-based session management to maintain secure, seamless user sessions.</li><li><strong>Security Enhancements</strong>: The team implemented multi-factor authentication (MFA) through Okta, adding another layer of security.</li></ul><h3>5. Testing and Quality Assurance</h3><p>Given the critical nature of authentication, thorough QA was essential. We adopted a combination of <strong>manual</strong> and <strong>automated testing</strong> strategies:</p><ul><li><strong>Functional Testing</strong>: Ensured all authentication flows worked as expected.</li><li><strong>Load Testing</strong>: Simulated high user traffic to validate system performance under stress.</li><li><strong>Security Testing</strong>: Collaborated with cybersecurity experts to identify any vulnerabilities in the SSO implementation.</li></ul><p>We also worked closely with our users during a beta phase to ensure the transition was smooth, addressing any issues before the final launch.</p><h3>6. Final Delivery and Post-Implementation Review</h3><p>The project was successfully delivered on time and within the allocated budget. The key success factors were careful upfront planning, continuous risk management, and iterative development using Scrum.</p><h4>Key Takeaways:</h4><ul><li><strong>Flexibility vs Simplicity</strong>: While other Okta integration options like SAML would have been faster, the flexibility of the Okta API ensured that we could fully tailor the solution to our existing monolithic architecture.</li><li><strong>Risk Management</strong>: Regular risk assessment using <strong>PMI principles</strong> helped us anticipate issues and adjust accordingly, keeping the project on track.</li><li><strong>Scrum Efficiency</strong>: The use of Scrum allowed us to remain agile, adapt to changing requirements, and maintain continuous stakeholder involvement.</li></ul><h3>7. Conclusion</h3><p>Implementing Okta SSO in a monolithic Java application posed a series of technical and managerial challenges. However, by leveraging <strong>PMI principles for project management</strong> and the <strong>Scrum framework for development</strong>, we were able to navigate those challenges effectively. The final solution not only enhanced security but also improved user experience.</p><p>If you’re managing a similar project, consider the following:</p><ul><li>Evaluate different integration options thoroughly and align them with your business needs.</li><li>Apply risk management strategies to anticipate and mitigate project roadblocks.</li><li>Use agile methodologies like Scrum to maintain flexibility and drive iterative progress.</li></ul><p>In the end, balancing technical requirements with strategic management principles is the key to delivering successful, secure, and scalable software solutions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1f46c5707b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>