<?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 Mifraz Murthaja on Medium]]></title>
        <description><![CDATA[Stories by Mifraz Murthaja on Medium]]></description>
        <link>https://medium.com/@mifrazmurthaja?source=rss-171d8e0afdf2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5FWHRLLlf_Uxa99TGs5nMw.png</url>
            <title>Stories by Mifraz Murthaja on Medium</title>
            <link>https://medium.com/@mifrazmurthaja?source=rss-171d8e0afdf2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:31:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mifrazmurthaja/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[The visibility of plain text credentials in the browser is not a vulnerability]]></title>
            <link>https://mifrazmurthaja.medium.com/the-visibility-of-plain-text-credentials-in-the-browser-is-not-a-vulnerability-5dc67162e98f?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5dc67162e98f</guid>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Thu, 08 Dec 2022 08:05:23 GMT</pubDate>
            <atom:updated>2022-12-12T04:27:30.119Z</atom:updated>
            <content:encoded><![CDATA[<p>Have you ever seen plain-text credentials in the browser? Do you think, it’s an application vulnerability?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcqMlAYoYSMMYh9KzOsz3g.png" /><figcaption>Network capture of submitting the credentials on Twitter</figcaption></figure><p>The direct answer would be, No. That’s how the protocol works and it’s the intended behavior of the browser.</p><h4>Well, let’s dig into the question, “WHY?”</h4><p>It’s not an application vulnerability, since it’s only visible in the particular user’s browser and the browser must be protected by the user. If someone else obtained access to your browser, they can do more than what you’re seeing on the browser.</p><p><a href="https://mifrazmurthaja.medium.com/the-role-of-cookies-in-session-management-542db416519a">The role of cookies in session management</a></p><h4>How does it work?</h4><p>Do you know there are 7 layers in the OSI model, which defines how computer systems communicate over a network?</p><p><a href="https://www.imperva.com/learn/application-security/osi-model/">What is OSI Model | 7 Layers Explained | Imperva</a></p><p>In the same context, the user interaction with the browser relies on the application layer (the top layer). Therefore, it’s the browser that receives the user input directly and transmits it through the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*vSvYs2dhTDM-ZucEJ96e9g.jpeg" /></figure><p>What we’re seeing on the network tracer is, the data we submitted to the browser, and the network tracer is part of the browser. Therefore, showing the credentials in plain text in the network tracer is expected, since that’s what we entered on the login page!</p><p>In addition to the network tracer, the credentials can also be seen in plain text if those are saved in the browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FBVy5viLGpwyzie6gGrlYA.gif" /></figure><p>Once the request leaves the browser (Presentation Layer), the whole <strong><em>POST</em></strong> request payload will be encrypted (between the OSI layers 6–4), including the credentials when communicated using <strong><em>HTTPS</em></strong>.</p><ul><li>Using <strong>HTTPS</strong> is mandatory since that’s the secure protocol to communicate over a network. If otherwise (HTTP) entire data will be sent in plain text throughout the network.</li><li>The credentials <strong>should not</strong> be sent as URL <strong>query parameters</strong> (GET), since the URL could be recorded in several places such as server logs.</li><li>The sensitive data must be sent as <strong>request body parameters</strong> (POST), or as <strong>request headers</strong> (POST/ GET).</li></ul><p><a href="https://stackoverflow.com/questions/45352550/sending-passwords-over-https-get-vs-post">Sending passwords over HTTPS: GET vs POST</a></p><h4>Is it possible to encrypt the credentials in the browser?</h4><p>The actual encryption of network communication happens in the OSI layers between 6–4, whereas the browser resides on layer 7 (application layer). Therefore, it’s not possible to encrypt the credentials in a standard way and such well-defined protocols are not available as of now.</p><h4>Oh, do you still think it must be possible?</h4><ol><li>Assume you’re encrypting the credential somehow, then the encrypted string will be your new password 😉 (If someone obtained the encrypted credentials, they could gain access to your account by using it — decryption is not required).</li><li>What if the server accepts the hashed credentials? Well, that’s your new credentials again 😉 (If someone obtained the hashed value of your password, they could gain access to your account by using the hashed value— the original value is not required, since the server is already accepting the hashed value as the password)</li></ol><p>A simple example is, the way Facebook sends the credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAyqJwb2njL1iUgbWcaqAg.png" /></figure><p>If I’ve provided the valid credentials (I haven’t 😇), you can gain access to my account, using the above values.</p><p>Yes, you can mimic the encryption behavior as above. However, if someone gains access to your network tracer (as a HAR file) or if the attacker is recording/ snooping your screen, they can access your account, even with the hashed/ encrypted credentials.</p><p>The same applies if you’re intercepting the traffic from the burp suite and viewing the request payload since it requires importing the certificate to your browser in order to create a different secure channel between the browser and the burp suite. If someone is able to add a certificate to your browser and proxy the network requests, they can do way more than what you think and you’re already on a MITM attack 😁</p><h4>Do you have a better approach?</h4><p>Research and publish it to the world!</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2022/12/the-visibility-of-plain-text.html">my blog</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5dc67162e98f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The role of cookies in session management]]></title>
            <link>https://mifrazmurthaja.medium.com/the-role-of-cookies-in-session-management-542db416519a?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/542db416519a</guid>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Thu, 01 Dec 2022 15:36:28 GMT</pubDate>
            <atom:updated>2022-12-12T04:29:16.548Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you in a confusion about cookie vs session? Simply, the cookie is used to track the user information on the <strong>client side</strong>, whereas the session is used to track the user information on the <strong>server side</strong>.</p><p>Since the HTTP protocol is stateless, implementing session management in a web application is inevitable, if it involves user interactions. In simple terms, the <strong>server will not be able to identify the user</strong> who makes the interaction without session management.</p><p>Let’s directly jump into the topic and see how the cookies are contributing to the session management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bYFh3VIelG5Fn1KxJi1lLA.png" /><figcaption>The authentication flow on Facebook without the cookies</figcaption></figure><ol><li><strong>Bob</strong> accesses facebook.com on his browser and provides the credentials on the login page to authenticate to facebook.com — Facebook creates a <strong>session for Bob </strong>on the server.</li><li><strong>Alice</strong> accesses facebook.com on her browser and provides the credentials on the login page to authenticate to facebook.com — Facebook creates a <strong>session for Alice</strong> on the server.</li><li>Currently, Facebook has the sessions of 2 users: Bob and Alice. If <strong>Bob interacts with Facebook</strong>, how will Facebook identify whether it’s <strong>Bob or Alice</strong>?</li></ol><p>That’s where the cookie comes into play in session management!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rL7lInMFfU3VJyt_VR3Htw.png" /><figcaption>The authentication flow on facebook with the cookies</figcaption></figure><p>Once an authenticated session is created for Bob on Facebook, it responds back with a <strong>set-cookie</strong> header, which stores the cookie on Bob’s browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TG5N8ey0mPY_i0s9ZF68HQ.png" /><figcaption>A sample <strong>set-cookie</strong> response header, which sets the <strong>c_user</strong> cookie returned by Facebook</figcaption></figure><p>Similarly, with the set-cookie header returned for Alice, the <strong>c_user</strong> cookie will be stored on Alice’s browser.</p><p>Now, both Bob and Alice are having their own cookies created on their browsers. Therefore, if Bob accesses Facebook, the c_user cookie will also be sent with the request to Facebook, which will be used by Facebook to identify the session stored on the server. Once the session is identified for the particular request, Facebook will be able to identify the user who interacts with Facebook and return the data of the particular user.</p><blockquote>It’s the browser’s responsibility to send whatever the cookies available for the patrticular domain to be sent along with any request made (Indeed, there are several other factors to be considered, whether a cookie should be sent with the request, even if the domain is matching. You may refer to the OWASP document below as a further reference).</blockquote><p><a href="https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/06-Session_Management_Testing/02-Testing_for_Cookies_Attributes">WSTG - Latest</a></p><blockquote>It’s not just the c_user cookie is used to identify the session but there are several other cookies are used by facebook to identify the user session on the browser. You can refer to the blog below to identify the cookies used by facebook.</blockquote><p><a href="https://techexpertise.medium.com/facebook-cookies-analysis-e1cf6ffbdf8a">Facebook Cookies Analysis</a></p><h3>A simple question!</h3><p>The cookies stored on the browser are used to identify the session stored on any server. Then, if you got a chance to obtain the cookies stored in Bob’s browser (by manipulating Bob) and store them in your browser, which user’s profile you’ll be seeing on your browser?</p><p>Indeed, it’ll be <strong>Bob’s profile</strong> (Try it by obtaining the cookies of another user’s browser for the facebook domain 😉).</p><p>Takeaway: Never share your cookies or provide access to your browser. Anyone can gain access to any of your accounts and keep using them until the particular session expires. Implementing MFA will not prevent this, since the cookies are reflections of perfectly authenticated sessions (the cookies are created after the user is authenticated successfully with all the MFA steps) — If you’ve shared the cookies, it implies you’ve shared your fully authenticated session.</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2022/12/the-role-of-cookies-in-session.html">my blog</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=542db416519a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing WSO2 Identity Server FIDO using Mobile Fingerprint]]></title>
            <link>https://mifrazmurthaja.medium.com/testing-wso2-identity-server-fido-using-mobile-fingerprint-668692fdeecd?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/668692fdeecd</guid>
            <category><![CDATA[fido]]></category>
            <category><![CDATA[identity-server]]></category>
            <category><![CDATA[wso2is]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Sat, 03 Apr 2021 11:40:27 GMT</pubDate>
            <atom:updated>2022-12-12T04:14:16.384Z</atom:updated>
            <content:encoded><![CDATA[<h3>Testing FIDO in WSO2 Identity Server using Mobile Fingerprint</h3><p>Let’s test the WSO2 Identity Server using the mobile phone, specifically <a href="https://is.docs.wso2.com/en/latest/learn/multi-factor-authentication-using-fido/">FIDO</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/922/1*RSYcUs605BQ2wENaqgbEow.png" /></figure><p><a href="https://is.docs.wso2.com/en/latest/learn/multi-factor-authentication-using-fido/">MFA using FIDO - WSO2 Identity Server Documentation</a></p><p>In the context of testing, it’s inevitable to access WSO2 IS using the mobile phone. Nevertheless, it involves several challenges such as,</p><ul><li>Cannot access WSO2 IS using localhost as we do on the PC.</li><li>Indeed, we can access using the private IP when we connect the mobile phone and the PC to the same network. However, there could be certificate issues due to mismatching of the common name (CN) / missing subject alternative names (SAN).</li><li>FIDO cannot be tested using the IP address as per the <a href="https://www.w3.org/TR/webauthn">spec</a>. Hence, it’s an obligatory requirement to have a domain name.</li></ul><p><a href="https://www.w3.org/TR/webauthn">Web Authentication: An API for accessing Public Key Credentials - Level 2</a></p><p>Well, let’s address the challenges successively: one at a time!</p><h3><strong>Access WSO2 IS using the IP address</strong></h3><p>This is pretty simple and we gotta do nothing other than connecting both PC and the mobile phone to the same WIFI/ LAN network.</p><p><strong>Accessing the management console</strong></p><ol><li>Start the WSO2 IS on your PC.</li><li>Get the private IP address of your PC (We can use ifconfig (MAC/ Linux) or ipconfig (Windows) to get the IP address. ex:192.168.1.101).</li><li>Connect both the PC and the Mobile phone to the same WIFI/ LAN network.</li><li>Access the WSO2 IS using the browser on your mobile phone. (https://192.168.1.101:9443/carbon)</li></ol><p>That’s it, you should be able to access the management console of WSO2 IS (You may get a certificate warning in the browser, which you can bypass by selecting <strong>Advanced</strong> and then clicking <strong>Proceed</strong>).</p><p><strong>Accessing the UserPortal or MyAccount</strong></p><p>Try accessing the UserPortal(https://192.168.1.101:9443/user-portal) —<em> IS 5.10.0</em> or MyAccount (https://192.168.1.101:9443/myaccount) — <em>IS 5.11.0 </em>from your mobile phone. However, this won’t work since,</p><p>When we access the UserPortal or MyAccount, it’ll internally build the authorization request URL using the hostname configured in the deployment.toml file. Therefore, though we’re accessing the WSO2 IS using the IP address, the authorization request will be made to localhost as follows.</p><pre><a href="https://192.168.1.101:9443/oauth2/authorize?response_type=cod">https://localhost:9443/oauth2/authorize?response_type=code</a>…</pre><p>Hence, in order to resolve it, we can simply change the hostname to the private IP address of the PC in the deployment.toml file.</p><pre>[server]<br>hostname = &quot;192.168.1.101&quot;</pre><p>Restart the server once the deployment.toml is updated. Moreover, we’ll have to update the callback URL as well in order to prevent the callback URL validation error (<em>Service Provider → List → Edit → Callback Url</em>)</p><pre>UserPortal: <a href="https://localhost:9443/myaccount/login|https://192.168.1.101:9443/myaccount/login">https://192.168.1.101:9443/user-portal/login</a><br>MyAccount: <a href="https://localhost:9443/myaccount/login|https://192.168.1.101:9443/myaccount/login">https://192.168.1.101:9443/myaccount/login</a></pre><p>Further, we should also update the Identity Provider Entity ID to align with the hostname (<em>Identity Providers → Inbound Authentication Configuration → OAuth2/OpenID Connect Configuration → Identity Provider Entity ID</em>) — The MyAccount requires updating this to prevent issuer validation failure in the ID token.</p><pre><a href="https://192.168.1.101:9443/oauth2/token">https://192.168.1.101:9443/oauth2/token</a></pre><p>That’s it! We’re good to access the UserPortal <a href="https://192.168.1.101:9443/myaccount">(https://192.168.1.101:9443/u</a>ser-portal) or MyAccount <a href="https://192.168.1.101:9443/myaccount">(https://192.168.1.101:9443/myaccount</a>) using the IP address from the mobile phone.</p><p>Well, out of curiosity, just try registering FIDO in the UserPortal or MyAccount by navigating to <em>Security → Multi-factor authentication → via Security Device</em> and it should fail as FIDO cannot be used with IP address as per the <a href="https://www.w3.org/TR/webauthn">spec</a>.</p><h3>Access WSO2 IS using a domain</h3><p>Prerequisites: Your router should support Dynamic DNS (Almost all the routers support it — Check for your router documentation).</p><p><strong>Resolving DNS</strong></p><ol><li>Create an account at <a href="http://www.noip.com/">www.noip.com</a> providing a hostname (ex: wso2is.ddns.net)</li><li>Click <strong>My Account.</strong></li><li>You may add a username and security question when it prompted (Optional).</li><li>Navigate to <em>Dynamic DNS → No-IP Hostnames → Click the hostname (wso2is.ddns.net)</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*osiWpSNB6jQMwpG4wfXCfQ.png" /></figure><p>5. Enter the private IP address of the PC (192.168.1.101).</p><p>6. Configure Dynamic DNS in your router to use the no-ip domain (Probably it should be at <em>Advanced → Network → Dynamic DNS</em>) — Check with your router documentation (You may provide the email address or the username you’ve configured as the username).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*r1FUxBCBvVT6h8d5YOBvtw.png" /></figure><p>That’s it! You should now be able to access the management console using the domain you’ve just configured(https://wso2is.ddns.net:9443/carbon).</p><p><strong>Changing the hostname in WSO2 IS</strong></p><p>Well, you can refer to <a href="https://is.docs.wso2.com/en/latest/setup/changing-the-hostname/">Changing the hostname</a> documentation for a detailed guide to change the hostname of WSO2 IS. Let’s see the necessary steps to change the hostname of WSO2 IS below (We cannot access the UserPortal or MyAccount without changing the hostname of WSO2 IS due to the reason mentioned earlier).</p><ol><li>Create a Keystore with the new hostname in &lt;IS_HOME&gt;/repository/resources/security directory.</li></ol><pre>keytool -genkey -alias wso2carbon -keyalg RSA -keysize 2048 -keystore wso2carbon_new.jks -dname &quot;CN=wso2is.ddns.net, OU=Home,O=Home,L=SL,S=WS,C=LK&quot; -storepass wso2carbon -keypass wso2carbon -validity 360</pre><p>2. Export the certificate from the Keystore.</p><pre>keytool -exportcert -keystore wso2carbon_new.jks -alias wso2carbon -file wso2carbon_new.crt</pre><p>3. Import the certificate to the client-truststore (Default password of the client-truststore is wso2carbon and type yes when it’s prompted to trust the certificate).</p><pre>keytool -importcert -keystore client-truststore.jks -alias wso2carbon_new -file wso2carbon_new.crt</pre><p>4. Change the hostname in deployment.toml.</p><pre>[server]<br>hostname = &quot;wso2is.ddns.net&quot;</pre><p>5. Restart the server.</p><p>6. Update the Identity Provider Entity ID (<em>Identity Providers → Inbound Authentication Configuration → OAuth2/OpenID Connect Configuration → Identity Provider Entity ID</em>).</p><pre><a href="https://wso2is.ddns.net:9443/oauth2/token">https://wso2is.ddns.net:9443/oauth2/token</a></pre><p>7. Update the callback URL of UserPortal or MyAccount (You may also use a regex if required).</p><pre>UserPortal: <a href="https://localhost:9443/myaccount/login|https://192.168.1.101:9443/myaccount/login|https://wso2is.ddns.net:9443/myaccount/login">https://wso2is.ddns.net:9443/user-portal/login</a><br>MyAccount: <a href="https://localhost:9443/myaccount/login|https://192.168.1.101:9443/myaccount/login|https://wso2is.ddns.net:9443/myaccount/login">https://wso2is.ddns.net:9443/myaccount/login</a></pre><p>Trust me, that’s it! Let’s access the UserPortal or MyAccount from your mobile phone!</p><pre>UserPortal: <a href="https://localhost:9443/myaccount/login|https://192.168.1.101:9443/myaccount/login|https://wso2is.ddns.net:9443/myaccount/login">https://wso2is.ddns.net:9443/user-porta</a>l<br>MyAccount: <a href="https://localhost:9443/myaccount/login|https://192.168.1.101:9443/myaccount/login|https://wso2is.ddns.net:9443/myaccount/login">https://wso2is.ddns.net:9443/myaccount</a></pre><p>Now you should be able to register FIDO using the mobile fingerprint by navigating to <em>Security → Multi-factor authentication → via Security Device </em>in your mobile phone.</p><p><strong>Known issue: </strong><a href="https://github.com/wso2/product-is/issues/11055">https://github.com/wso2/product-is/issues/11055</a> (Fixed in the latest update of WSO2 IS 5.10 and 5.11)</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2021/04/testing-wso2-identity-server-fido-using.html">my blog</a>!</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=668692fdeecd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Account Lock Countdown in WSO2 Identity Server]]></title>
            <link>https://mifrazmurthaja.medium.com/account-lock-countdown-in-wso2-identity-server-4d468ad2fe30?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d468ad2fe30</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[account-lock]]></category>
            <category><![CDATA[identity-server]]></category>
            <category><![CDATA[wso2is]]></category>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Tue, 09 Feb 2021 19:52:27 GMT</pubDate>
            <atom:updated>2022-12-12T04:15:39.680Z</atom:updated>
            <content:encoded><![CDATA[<h3>Let the Countdown begin when the account is locked!</h3><p><em>Customizing the login page to implement a countdown for the locked users in WSO2 Identity Server.</em></p><p>Enabling the <strong>Account Locking due to Failed Login Attempts</strong> feature helps prevent brute-forcing for user credentials for an account. However, implementing a security feature always impacts the legit user’s user experience and is indispensable to maintain user-friendliness. With the context of maintaining the balance between ease of use and the security measure, this blog demonstrates implementing a customization to run a countdown for when the account will be unlocked for the locked user account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*dAozH_otSXWQX9szrvQVJg.png" /></figure><p><strong>Step 1: deployment.toml</strong></p><p>Add the configuration below in deployment.toml file to return the error reason.</p><pre>[authentication.authenticator.basic.parameters]<br>showAuthFailureReason = true</pre><p><a href="https://is.docs.wso2.com/en/5.11.0/develop/customizing-authentication-error-messages/">Customizing Authentication Error Messages - WSO2 Identity Server Documentation</a></p><p>However, enabling this may lead to user enumeration vulnerability, since this will usually return 3 main types of error codes listed below.</p><ul><li>Invalid User (17001)</li><li>Invalid credentials (17002)</li><li>Account Lock (17003)</li></ul><p>We’ll only be using the error code: 17003 in this customization. Brute-forcing the password for a single account (17002) can be prevented by enabling the reCaptcha feature. However, enumerating the username (17001) should be handled externally such as using WAF (As similar to handling DOS/ DDOS at WAF level).</p><p><a href="https://is.docs.wso2.com/en/5.11.0/learn/configuring-recaptcha-for-single-sign-on/">Configuring reCaptcha for Single Sign On - WSO2 Identity Server Documentation</a></p><p><strong>Step 2: Enable Account Locking due to Failed Login Attempts</strong></p><p>Enable account locking by Navigating to <em>Identity Provider</em> ➜ <em>Login Attempts Security</em> ➜ <em>Account Lock</em> and enable <em>Lock user accounts</em> in the management console (<a href="https://localhost:9443/carbon">https://localhost:9443/carbon</a>).</p><p><a href="https://is.docs.wso2.com/en/5.11.0/learn/configuring-account-locking-due-to-failed-login-attempts/">Failed Login Attempts - WSO2 Identity Server Documentation</a></p><p><strong>Step 3: Customized retry.jsp</strong></p><p>With the changes above, if a user tries to login when the user account is locked, the user will be redirected to retry.do (retry.jsp) page with the additional parameters indicated below.</p><pre>failedUsername=user1&amp;errorCode=17003&amp;remainingAttempts=0</pre><p>We’ll be using the above parameters to retrieve the account-lock related user information required for the countdown implementation in retry.jsp. If you haven’t made any changes to the default retry.jsp resides in the authentication endpoint, you can just replace the retry.jsp file with the updated-retry.jsp provided below in <em>&lt;IS_HOME&gt;/repository/deployment/server/webapps/authenticationendpoin </em>directory.</p><ul><li>IS 5.10: <a href="https://gist.github.com/mifrazmurthaja/bbc9512ac73295967453af3ff7846ab4"><strong><em>updated-retry.jsp</em></strong></a></li><li>IS 5.11: <a href="https://gist.github.com/mifrazmurthaja/4373e27e1218c88a59d46067ee4a29f0"><strong><em>updated-retry.jsp</em></strong></a></li></ul><p>If you’ve already made any customizations in the retry.jsp, let’s move on to <em>Step 3.1 </em>to implement the countdown on top of the existing customizations.</p><p><strong>Step 3.1: Customizing the Authentication Endpoint (retry.jsp)</strong></p><ol><li>Import the packages below.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f11e8f4c4f3da9f3cdbcc34d85ce6da/href">https://medium.com/media/5f11e8f4c4f3da9f3cdbcc34d85ce6da/href</a></iframe><p>2. Add the code snippet below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/09bffc526a6fc71a31bad7639dd41048/href">https://medium.com/media/09bffc526a6fc71a31bad7639dd41048/href</a></iframe><p>3. Find the div element below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/905174660e1ae912d42b7fcb77f859e3/href">https://medium.com/media/905174660e1ae912d42b7fcb77f859e3/href</a></iframe><p>4. Replace the above with the element provided below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1efe0e44caead22ffd0033433eaaed92/href">https://medium.com/media/1efe0e44caead22ffd0033433eaaed92/href</a></iframe><p>5. Add the script provided below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/673336574919c19dabe669dfea213b0f/href">https://medium.com/media/673336574919c19dabe669dfea213b0f/href</a></iframe><p>That’s it! Let’s test by simply accessing the MyAccount or User-Portal and provide the invalid credentials until it reaches the maximum failed login attempts configured in the account locking settings (Default: 5).</p><ul><li>IS 5.10: User-Portal (<a href="https://localhost:9443/user-portal">https://localhost:9443/user-portal</a>)</li><li>IS 5.11: MyAccount (<a href="https://localhost:9443/myaccount">https://localhost:9443/myaccount</a>)</li></ul><p>This customization is gently tested with,</p><ul><li>IS Version: 5.10 and 5.11</li><li>Single-Tenant and Multi-Tenancy environments</li></ul><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2021/02/account-lock-countdown-in-wso2.html">my blog</a>!</p><p>Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d468ad2fe30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implement SSO for Zendesk using WSO2 Identity Server]]></title>
            <link>https://mifrazmurthaja.medium.com/implement-sso-for-zendesk-using-wso2-identity-server-a32148313e5c?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a32148313e5c</guid>
            <category><![CDATA[sso]]></category>
            <category><![CDATA[wso2is]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[identity]]></category>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Sun, 31 May 2020 15:51:15 GMT</pubDate>
            <atom:updated>2022-12-12T04:17:05.236Z</atom:updated>
            <content:encoded><![CDATA[<p>Implementing SSO for Zendesk Customer Support Ticket System using WSO2 Identity Server<em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Df1budjeUU034VJJZe_P6g.png" /></figure><p>Zendesk is one of the major support, sales, and customer engagement software that enables businesses to quickly implement and easily scales to meet changing needs. But as providing support is a part of your business, your organization might have plenty of other applications that are used by your employees or users regularly apart from the Zendesk system. Hence, implementing a single point of authentication (<strong>Single Sign-On — SSO</strong>) with Zendesk and other applications will enhance the user experience heavily for your users, and it has become an obligatory requirement in the world. That’s where the WSO2 Identity Server comes into play with plenty of other <em>Identity and Access Management</em> solutions! We can integrate SSO for Zendesk easily using the WSO2 Identity Server just like adding a service provider.</p><p>Zendesk provides the SSO feature through SAML and JWT SSO protocols. This article focuses on implementing SSO for Zendesk using the <strong>JWT SSO </strong>protocol. If you want to implement SSO for Zendesk using the SAML protocol, you may refer to the below documentation.</p><p><a href="https://is.docs.wso2.com/en/5.10.0/learn/configuring-saml2-web-single-sign-on/">Configuring SAML2 Web Single-Sign-On - WSO2 Identity Server Documentation</a></p><p><strong>Wanna know how the JWT SSO works?</strong></p><p><a href="https://medium.com/@mifrazmurthaja/jwt-sso-with-wso2-identity-server-cf486ffba1bf">JWT SSO with WSO2 Identity Server</a></p><h3>Let’s start with configuring the Zendesk application</h3><ol><li>In your Zendesk site, click the Zendesk Products icon in the top bar and select <strong>Admin Center</strong>.</li><li>Click the <strong>Security</strong> icon in the left sidebar or click on the <strong>Security settings</strong> and select the <strong>Single sign-on</strong> tab.</li><li>Click <strong>Edit/ Configure </strong>for <strong>JSON Web Token.</strong></li><li>Select the <strong>Enabled</strong> checkbox.</li><li>Enter the below URL for the Remote login URL. Wondering how this <strong><em>jwtRP=zendesk</em></strong> jump into here? No worries, that’s the Relying Party name, which we’re going to configure in the WSO2 Identity Server!</li></ol><pre><a href="https://localhost:9443/identity/jwtsso?jwtRP=zendesk">https://localhost:9443/identity/jwtsso?jwtRP=zendesk</a></pre><p>6. Enter the below URL for the Remote logout URL.</p><pre><a href="https://localhost:9443/identity/jwtsso/logout?jwtRP=zendesk">https://localhost:9443/identity/jwtsso/logout?jwtRP=zendesk</a></pre><p>7. Make a copy of the shared secret and <strong>Save</strong> your changes. If the <strong>Shared secret</strong> is not in plain text (It’ll be masked once you saved your changes), you’ll have to click <strong>Edit/ Configure</strong> next to <strong>JSON Web Token</strong> again to reopen the configuration and will have to disable and enable the JSON Web Token configuration.</p><p>8. Select the <strong>End users</strong> tab on the same page (<strong>Security settings</strong>) and enable external authentication by selecting the <strong>External authentication</strong> checkbox.</p><p>9. <strong>Save</strong> the changes.</p><p>Take a note of the below and we’ll be using it when we configure the Service Provider in the WSO2 Identity Server.</p><p><strong>1. Site URL</strong></p><p>The site URL of your Zendesk application. It will look something like below.</p><pre><strong>https://<em>subdomain</em>.zendesk.com</strong></pre><p><strong>2. API Key (Shared Secret)</strong></p><p>The Shared secret we’ve obtained above when we enabling the <strong>JSON Web Token</strong> SSO on the Zendesk application.</p><p>You may refer below for more details on enabling SSO for Zendesk.</p><p><a href="https://support.zendesk.com/hc/en-us/articles/203663816-Enabling-JWT-JSON-Web-Token-single-sign-on">Enabling JWT (JSON Web Token) single sign-on</a></p><h3>Let’s configure WSO2 Identity Server</h3><p>It’s time to get WSO2 Identity Server 5.10 if you haven’t done yet.</p><p><a href="https://wso2.com/identity-and-access-management/">WSO2 Identity and Access Management</a></p><p>Get the connector from the WSO2 IS connector store.</p><p><a href="https://store.wso2.com/store/assets/isconnector/details/25bdf0b9-2584-4306-9872-831eaaebe7cd">IS Connector | WSO2 Store</a></p><p>Let’s download the jar file and place it inside the below directory.</p><pre>&lt;IS_HOME&gt;/repository/components/dropins</pre><p>Add the configuration below in deployment.toml file resides in &lt;IS_HOME&gt;/repository/conf directory and start the server (restart if the server is already up and running).</p><pre>[[resource.access_control]]<br>context=&quot;/identity(.*)&quot;<br>secure=&quot;false&quot;<br>http_method=&quot;GET&quot;</pre><p>If you’re new to WSO2 Identity Server, you may refer below to run the product.</p><p><a href="https://is.docs.wso2.com/en/5.10.0/setup/running-the-product/">Running the Product - WSO2 Identity Server Documentation</a></p><p>Once the server is up and running, access the management console at <a href="https://localhost:9443/carbon">https://localhost:9443/carbon</a> and login with the admin credentials (The default credentials would be <em>admin:admin</em>).</p><h4>Let’s configure the service provider as depicted below.</h4><p>Navigate to <em>Main </em>➜<em> Service Providers </em>➜<em> Add</em> and register a new service provider in the WSO2 IS management console.</p><p>Then navigate to <em>Inbound Authentication Configuration </em>➜<em> JWT SSO Configuration.</em> The <strong><em>JWT SSO Configuration</em></strong> is the one we’ve added newly by placing the jar in the <em>dropins</em> directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gtHQg8ewxf66Atm_jRWTw.png" /><figcaption>JWT SSO Sample Configurations</figcaption></figure><p>Enter <strong>zendesk</strong> for <strong>Relying Party</strong> and enter the <strong>Endpoint API</strong> and the <strong>API Key (Shared secret) </strong>which we’ve obtained from Zendesk portal.</p><p>Enter a <strong>Logout URL</strong> to redirect the user after the successful logout in the WSO2 Identity Server.</p><p>The below table describes the properties used in the JWT SSO inbound authenticator and the sample values related to those properties.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e93cce279a364cb459ac06946f1478f0/href">https://medium.com/media/e93cce279a364cb459ac06946f1478f0/href</a></iframe><p>Once you’ve completed configuring the JWT SSO configuration, we have to configure the claims required by Zendesk to create and identify the user. As per the Zendesk documentation, the below claims are mandatory and you may refer to the Zendesk documentation for other supported attributes.</p><ul><li><strong>email (required)</strong> - Email of the user being signed in, used to uniquely identify the user record in Zendesk Support.</li><li><strong>name (required) </strong>- The name of this user. The user in Zendesk Support will be created or updated in accordance with this.</li></ul><p>Apart from the above claims, the <strong>iat</strong> and the <strong>jti</strong> attributes are mandatory which are always included in the JWT token generated by the JWT SSO authenticator by default.</p><p>Let’s configure the claims in the WSO2 Identity Server SP claims configuration as follows.</p><ol><li>Navigate to the Service Provider you’ve created earlier and expand the <strong><em>Claim Configuration</em></strong> section.</li><li>Select <strong><em>Define Custom Claim Dialect</em></strong> as the <strong><em>Claim mapping Dialect.</em></strong></li><li>Define the <strong><em>Service Provider Claims</em></strong> (as required by Zendesk) and the related <strong><em>Local Claims</em></strong> (Claims available in WSO2 Identity Server) as below. (This is required to include the user claims in the JWT token; otherwise, no attributes will be included in the JWT token apart from the default attributes such as <strong>exp</strong> and <strong>iat</strong>.) Also, mark those claims as <strong><em>Requested Claim</em></strong> and <strong><em>Mandatory Claim</em></strong> so that the user will be prompted to add the claim value if it is not set for the particular user.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IvwR7e88eC1d6B7ESEg5Nw.png" /><figcaption>The service provider claim configuration</figcaption></figure><p>That’s! We’re good to start testing!</p><p>Let’s try to authenticate to Zendesk by clicking the Login button of Zendesk. You should be prompted with the login page of WSO2 Identity Server if you’re not already authenticated and once you’re authenticated, you should directly be redirected to the Zendesk application without prompting the Login page of Zendesk. Further, if you do not have an account on Zendesk with the provided email, an account will be created for you (user will be provisioned) by Zendesk with the claim values we’ve configured above.</p><p>In case if you had any issues with signing into your application due to any invalid configurations, you’re still able to login to Zendesk by accessing the below URL.</p><pre><a href="https://mifraz.zendesk.com/access/normal">https://subdomain.zendesk.com/access/normal</a></pre><p>Also, test the logout flow by Signing out from the Zendesk application. Once you click on the Sign out button in Zendesk, your session should be terminated from WSO2 Identity Server as well as from the Zendesk. You can verify whether your session on WSO2 Identity Server is terminated by making the authentication request again and you should be prompted with the login page of WSO2 Identity Server if the session is terminated successfully.</p><p>If you got any error message in Zendesk after the successful authentication in WSO2 Identity Server, there is a high chance you haven’t configured the claims properly in the claim configuration section of the service provider. However, if you got any errors in WSO2 Identity Server during the authentication process, you’ll have to refer to the below section too!</p><h4>Having any issues? Let’s debug!</h4><p>If you got any error while testing the flow, an error log or an exception should be logged in the wso2carbon log which will help you identify the cause for the issue. If you’re running the server as a background process or as a system service, you may have a look at the wso2carbon log file as follows.</p><pre>tail -f &lt;IS_HOME&gt;/repository/logs/wso2carbon.log</pre><p>However, if you’re still unclear on the error, we may dig a little deeper into the flow of the authentication process by enabling the debug level logs.</p><p>1. Add the below lines in the <em>log4j2.properties</em> file resides in <em>&lt;IS_HOME&gt;/repository/conf</em> directory.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ac8d1bbc7548e441191d257c7e14f3b9/href">https://medium.com/media/ac8d1bbc7548e441191d257c7e14f3b9/href</a></iframe><p>2. Append the <strong><em>org-wso2-carbon-identity-sso-jwt</em></strong><em> </em>to <strong><em>loggers</em></strong> variable as follows.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb3a96c27aef169eb02faa7da4ac2c43/href">https://medium.com/media/cb3a96c27aef169eb02faa7da4ac2c43/href</a></iframe><p>That’s it! The loggers will be updated in the runtime (Restart is not required) and you’ll see the debug level logs printing in the wso2carbon log when you try the flow again. I believe it’ll help you find the cause of the issue.</p><p>If all goes well, we’re done implementing SSO for Zendesk using WSO2 Identity Server!</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2020/07/implement-sso-for-zendesk-using-wso2.html">my blog</a>!</p><p>Cheers!</p><h3>References</h3><ul><li><a href="https://medium.com/@mifrazmurthaja/jwt-sso-with-wso2-identity-server-cf486ffba1bf">JWT SSO with WSO2 Identity Server</a></li><li><a href="https://github.com/wso2-extensions/identity-inbound-auth-jwtsso">GitHub - wso2-extensions/identity-inbound-auth-jwtsso: An Inbound Authenticator based on JWT</a></li><li><a href="https://support.zendesk.com/hc/en-us/articles/203663816-Enabling-JWT-JSON-Web-Token-single-sign-on">Enabling JWT (JSON Web Token) single sign-on</a></li><li><a href="https://mifraz.murthaja.com/2020/07/implement-sso-for-zendesk-using-wso2.html">Implement SSO for Zendesk using WSO2 Identity Server</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a32148313e5c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrate Thinkific LMS with WSO2 Identity Server]]></title>
            <link>https://mifrazmurthaja.medium.com/integrate-thinkific-lms-with-wso2-identity-server-53017f59bbff?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/53017f59bbff</guid>
            <category><![CDATA[thinkific]]></category>
            <category><![CDATA[identity-server]]></category>
            <category><![CDATA[wso2is]]></category>
            <category><![CDATA[sso]]></category>
            <category><![CDATA[mls]]></category>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Sat, 23 May 2020 10:02:07 GMT</pubDate>
            <atom:updated>2024-07-08T09:06:24.835Z</atom:updated>
            <content:encoded><![CDATA[<h3>Implement SSO for Thinkific LMS using WSO2 Identity Server</h3><p><em>Implementing SSO for Thinkific LMS using WSO2 Identity Server.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PmzpaVrw2lwPElAnpdyo8w.png" /></figure><p>Update: Thinkific now supports SSO with OIDC. Therefore, the connector suggested in this blog is no longer necessary. You can simply configure it as a <a href="https://is.docs.wso2.com/en/latest/references/app-settings/oidc-settings-for-app">regular OIDC application</a>.</p><p>Thinkific is a software platform that enables entrepreneurs to create, market, sell, and deliver their own online courses. Besides that, if you have multiple applications in your organization and if you want to implement a single point of authentication platform (Single Sign-On) for your users including the Thinkific LMS, WSO2 Identity Server provides it acting as an Identity Provider. Put differently, WSO2 Identity Server provides the capability of implementing SSO for Thinkific LMS which lets the users sign in to Thinkific LMS in a similar way the users sign in to other applications.</p><p><strong>Wanna understand how it works?</strong></p><p><a href="https://medium.com/@mifrazmurthaja/jwt-sso-with-wso2-identity-server-cf486ffba1bf">JWT SSO with WSO2 Identity Server</a></p><h3><strong>Let’s start configuring the LMS</strong></h3><p>There is nothing specifically to configure on the Thinkific LMS except customizing the UI. Let’s customize the UI in the latter part of this article.</p><p>For now, let’s get the configuration details from LMS to integrate LMS with WSO2 Identity Server by signing into the admin portal of Thinkific LMS. Take a note of the below and we’ll be using it when we configure the Service Provider in the WSO2 Identity Server.</p><p><strong>1. Site URL</strong></p><p>The site URL of your Thinkific application can be found at <em>Settings </em>➜<em> Site </em>➜<em> Site URL</em> section in the admin portal. It will look something like below.</p><pre><strong>https://your-school.thinkific.com</strong></pre><p>Otherwise, there will be a custom site URL if you have configured a custom site URL for your Thinkific LMS.</p><p><strong>2. API Key</strong></p><p>The API Key of your Thinkific application can be found at Settings ➜ Code &amp; analytics ➜ API section in the admin portal.</p><h3>Let’s configure WSO2 Identity Server</h3><p>It’s time to get WSO2 Identity Server 5.10 if you haven’t done yet.</p><p><a href="https://wso2.com/identity-and-access-management/">WSO2 Identity and Access Management</a></p><p>Get the connector from the WSO2 IS connector store.</p><p><a href="https://store.wso2.com/store/assets/isconnector/details/25bdf0b9-2584-4306-9872-831eaaebe7cd">IS Connector | WSO2 Store</a></p><p>Let’s download the jar file and place it inside the below directory.</p><pre>&lt;IS_HOME&gt;/repository/components/dropins</pre><p>Add the configuration below in deployment.toml file resides in &lt;IS_HOME&gt;/repository/conf directory and start the server (restart if the server is already up and running).</p><pre>[[resource.access_control]]<br>context=&quot;/identity(.*)&quot;<br>secure=&quot;false&quot;<br>http_method=&quot;GET&quot;</pre><p>If you’re new to WSO2 Identity Server, you may refer below to run the product.</p><p><a href="https://is.docs.wso2.com/en/5.10.0/setup/running-the-product/">Running the Product - WSO2 Identity Server Documentation</a></p><p>Once the server is up and running, access the management console at <a href="https://localhost:9443/carbon">https://localhost:9443/carbon</a> and login with the admin credentials (The default credentials would be <em>admin:admin</em>).</p><h4>Let’s configure the service provider as depicted below.</h4><p>Navigate to <em>Main </em>➜<em> Service Providers </em>➜<em> Add</em> and register a new service provider in the WSO2 IS management console.</p><p>Then navigate to <em>Inbound Authentication Configuration </em>➜<em> JWT SSO Configuration.</em> The <strong><em>JWT SSO Configuration</em></strong> is the one we’ve added newly by placing the jar in the <em>dropins</em> directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ONMOudRDj_DjI1A_NJJnKw.png" /><figcaption>JWT SSO Sample Configurations</figcaption></figure><p>Enter <strong>lms-test-app</strong> for <strong>Relying Party</strong> and enter the <strong>Endpoint API</strong> and the <strong>API Key</strong> which we’ve obtained from Thinkific LMS.</p><p>The below table describes the properties used in the JWT SSO inbound authenticator and the sample values related to those properties.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/154c8b7672edc79a42413a1447b92513/href">https://medium.com/media/154c8b7672edc79a42413a1447b92513/href</a></iframe><p>Regarding the Logout URL, the Thinkific LMS does not have a logout endpoint to terminate the particular user’s session by sending the user session identifier, instead, it has the logout URL which should be invoked through the browser which will terminate the user session based on the cookies sent along with the request.</p><p>Therefore, in this scenario, when the user clicks on the Sign-out button of LMS, the logout request will be sent to WSO2 IS and it’ll terminate the session on exists on the WSO2 IS. Once the user session is terminated on the WSO2 IS, it will make a redirection call to the Logout URL specified and hence the LMS session will also be terminated.</p><p>Once you&#39;ve completed configuring the JWT SSO configuration, we have to configure the claims required by Thinkific LMS to create and identify the user. As per the Thinkific Documentation, the below claims are supported by Thinkific LMS.</p><ul><li><strong>email (required)</strong> — the email of the authenticated user. If external_id is not supplied, email will be used as the unique identifier.</li><li><strong>first_name (required)</strong>- the first name of the authenticated user.</li><li><strong>last_name (required)</strong>- the last name of the authenticated user.</li><li><strong>iat (required)</strong> — must be the number of seconds since UNIX epoch. This is essentially the time that the JWT payload was issued.</li><li><strong>external_id</strong> — an identifier for the authenticated user. This is typically the id of the user in your system. This is OPTIONAL, but if supplied will be used as the unique identifier of the user. What this means is that when your student is trying to log in and you have included external_id in the payload, the Thinkific database will look for a user with that external_id. If that user is not found, the system will attempt to create them.</li><li><strong>bio</strong> — a textual bio of the user. This is OPTIONAL.</li><li><strong>company</strong> — the user’s company. This is OPTIONAL.</li><li><strong>timezone</strong> — the user’s timezone abbreviation (as defined here: <a href="https://www.iana.org/time-zones">https://www.iana.org/time-zones</a>). This is OPTIONAL.</li></ul><p>Let’s configure the mandatory claims in the WSO2 Identity Server SP claims configuration as follows.</p><ol><li>Navigate to the Service Provider you’ve created earlier and expand the <strong><em>Claim Configuration</em></strong> section.</li><li>Select <strong><em>Define Custom Claim Dialect</em></strong> as the <strong><em>Claim mapping Dialect.</em></strong></li><li>Define the <strong><em>Service Provider Claims</em></strong> (as required by Thinkific LMS) and the related <strong><em>Local Claims</em></strong> (Claims available in WSO2 Identity Server) as below. (This is required to include the user claims in the JWT token; otherwise, no attributes will be included in the JWT token apart from the default attributes such as <strong>exp</strong> and <strong>iat</strong>.) Also, mark those claims as <strong><em>Requested Claim</em></strong> and <strong><em>Mandatory Claim</em></strong> so that the user will be prompted to add the claim value if it is not set for the particular user.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*39Y38gNlMOWzQY-QCZ44qQ.png" /><figcaption>The service provider claim configuration</figcaption></figure><p>That’s! We’re good to start testing the configurations before we do the customizations on Thinkific LMS.</p><p>Let’s make an authentication request to WSO2 Identity Server as follows.</p><pre><a href="https://localhost:9443/identity/jwtsso?jwtRP=lms-test-app">https://localhost:9443/identity/jwtsso?jwtRP=lms-test-app</a></pre><p>Now you should be prompted with the login page of WSO2 Identity Server if you’re not already authenticated and once you’re authenticated, you should directly be redirected to the Thinkific LMS without prompting the Login page of Thinkific. Further, if you do not have an account on Thinkific LMS, an account will be created for you (user will be provisioned) by Thinkific LMS with the claim values we’ve configured above.</p><p>Let’s test the logout flow by making the request as follows.</p><pre><a href="https://localhost:9443/identity/jwtsso/logout?jwtRP=zendesk">https://localhost:9443/identity/jwtsso/logout?jwtRP=</a><a href="https://localhost:9443/identity/jwtsso?jwtRP=lms-test-app">lms-test-app</a></pre><p>Once you make the above request, your session should be terminated from WSO2 Identity Server as well as from the Thinkific LMS. You can verify whether your session on WSO2 Identity Server is terminated by making the authentication request again and you should be prompted with the login page of WSO2 Identity Server if the session is terminated successfully.</p><p>If all goes well, we’re good to start customizing the Thinkific LMS theme to redirect the users to WSO2 Identity Server for authentication.</p><p>If you got any error message in Thinkific LMS after the successful authentication in WSO2 Identity Server, there is a high chance you haven’t configured the claims properly in the claim configuration section of the service provider. However, if you got any errors in WSO2 Identity Server during the authentication process, you’ll have to refer to the below section too!</p><h4>Having any issues? Let’s debug!</h4><p>If you got any error while testing the flow, an error log or an exception should be logged in the wso2carbon log which will help you identify the cause for the issue. If you’re running the server as a background process or as a system service, you may have a look at the wso2carbon log file as follows.</p><pre>tail -f &lt;IS_HOME&gt;/repository/logs/wso2carbon.log</pre><p>However, if you’re still unclear on the error, we may dig a little deeper into the flow of the authentication process by enabling the debug level logs.</p><p>1. Add the below lines in the <em>log4j2.properties</em> file resides in <em>&lt;IS_HOME&gt;/repository/conf</em> directory.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ac8d1bbc7548e441191d257c7e14f3b9/href">https://medium.com/media/ac8d1bbc7548e441191d257c7e14f3b9/href</a></iframe><p>2. Append the <strong><em>org-wso2-carbon-identity-sso-jwt</em></strong><em> </em>to <strong><em>loggers</em></strong> variable as follows.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb3a96c27aef169eb02faa7da4ac2c43/href">https://medium.com/media/cb3a96c27aef169eb02faa7da4ac2c43/href</a></iframe><p>That’s it! The loggers will be updated in the runtime (Restart is not required) and you’ll see the debug level logs printing in the wso2carbon log when you try the flow again. I believe it’ll help you find the cause of the issue.</p><h3><strong>Let’s customize the Thinkific LMS</strong></h3><p>Let’s customize the Thinkific LMS sign-in and sign-up buttons to redirect the users to WSO2 Identity Server for authentication. Before we dig into the customization on a production setup of Thinkific LMS, I’d recommend contacting Thinkific LMS support if you have any concerns or clarifications.</p><p>You can learn more about Thinkific LMS customization on the Thinkific developer documentation below.</p><p><a href="https://developers.thinkific.com/themes/customizing-themes/">Getting Started With Themes</a></p><p>The customization explained below focuses on the <strong>Empire theme</strong> of Thinkific LMS.</p><ol><li>Navigate to <strong><em>snippets</em></strong> directory and open the <strong><em>meta_tags.liquid</em></strong> file.</li><li>Navigate to following sections and add the simple javascript codes as below to implement the redirect.</li></ol><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2a1764bdf08a327084be05e9ded8f243/href">https://medium.com/media/2a1764bdf08a327084be05e9ded8f243/href</a></iframe><p>To be honest, I haven’t tested the Thinkific LMS customization yet.</p><p>If all goes well, we’re done integrating Thinkific LMS with WSO2 Identity Server!</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2020/07/implement-sso-for-thinkific-lms-using.html">my blog</a>!</p><p>Cheers!</p><h3>References</h3><ul><li><a href="https://medium.com/@mifrazmurthaja/jwt-sso-with-wso2-identity-server-cf486ffba1bf">JWT SSO with WSO2 Identity Server</a></li><li><a href="https://github.com/wso2-extensions/identity-inbound-auth-jwtsso">GitHub - wso2-extensions/identity-inbound-auth-jwtsso: An Inbound Authenticator based on JWT</a></li><li><a href="https://developers.thinkific.com/themes/customizing-themes/">Getting Started With Themes</a></li><li><a href="https://support.thinkific.com/hc/en-us/articles/360030718713-SSO-Automatically-Sign-in-From-Your-Own-Website">SSO - Automatically Sign in From Your Own Website</a></li><li><a href="https://mifraz.murthaja.com/2020/07/implement-sso-for-thinkific-lms-using.html">Implement SSO for Thinkific LMS using WSO2 Identity Server</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53017f59bbff" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JWT SSO with WSO2 Identity Server]]></title>
            <link>https://mifrazmurthaja.medium.com/jwt-sso-with-wso2-identity-server-cf486ffba1bf?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf486ffba1bf</guid>
            <category><![CDATA[wso2is]]></category>
            <category><![CDATA[mls]]></category>
            <category><![CDATA[sso]]></category>
            <category><![CDATA[thinkific]]></category>
            <category><![CDATA[wso2-identity-server]]></category>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Fri, 22 May 2020 09:52:33 GMT</pubDate>
            <atom:updated>2022-12-12T04:18:41.183Z</atom:updated>
            <content:encoded><![CDATA[<p><em>An inbound authentication protocol to implement JWT based SSO for your application with WSO2 Identity Server.</em></p><p>Before we dive into the topic, I hope you know the terms, <a href="https://jwt.io/introduction/">JWT</a> and <a href="https://is.docs.wso2.com/en/5.10.0/get-started/single-sign-on-and-identity-federation/">SSO</a>.</p><p>You may aware of the protocols used to implement SSO on your application such as SAML and OpenID Connect (OIDC). Those are well-known protocols used to implement SSO and almost all the identity providers support it. You may refer <a href="https://is.docs.wso2.com/en/5.10.0/learn/configuring-single-sign-on/">configuring SSO in WSO2 Identity Server</a> though.</p><p>In the same context, the JWT SSO is a kind of protocol used to implement SSO on your application.</p><h3><strong>In a concise manner,</strong></h3><p>We can say, the JWT SSO is an authentication protocol used to authenticate the user based on the JWT token. In other words, the application relies on the JWT token and uses the JWT token as the source of authentication in the SSO flow. As an example, the <a href="https://support.thinkific.com/hc/en-us/articles/360030718713-SSO-Automatically-Sign-in-From-Your-Own-Website">Thinkific LMS</a> and <a href="https://support.zendesk.com/hc/en-us/articles/203663816-Enabling-JWT-JSON-Web-Token-single-sign-on">Zendesk Support Ticket System</a> provide the SSO feature through the JWT SSO protocol.</p><p>The high-level architecture of the authentication flow can be depicted using the below diagram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*ZAeHs-5z858F84TqhgLIsQ.png" /><figcaption>High-level Architecture</figcaption></figure><p>In general, those applications require an authentication request to be made as follows.</p><pre>https://applicationdomain.com/jwt?<strong>jwt={payload}</strong></pre><p>Once the application receives the JWT token, it verifies the JWT token, get the user claims from the JWT token and it will let the user sign in to the application without prompting the sign-in page of the application as it believes the user is already authenticated using the Identity Provider, in this scenario the WSO2 Identity Server.</p><h3><strong>Let’s dive into the topic!</strong></h3><p>Let’s take a scenario, where your organization is having multiple applications and to avoid signing into the application separately, you’re implementing SSO with an Identity Provider, which lets the users sign into the identity provider once and the identity provider will let the user sign in to all the required applications without prompting the sign-in page again and again (Basically the advantage of SSO).</p><h4><strong>How the JWT token comes into play in existing SSO architecture?</strong></h4><p>Let’s assume you want to implement SSO for an application, which requires the JWT token as the source of authentication. A most common example would be the <a href="https://www.thinkific.com/">Thinkific LMS</a> as it supports implementing SSO only using the JWT SSO protocol.</p><p>Since it is not using a common SSO protocol like OIDC or SAML, we’ll have to put an extra effort to implement SSO among all the other applications in the existing architecture. However, <strong><em>with WSO2 Identity Server, you can easily integrate SSO into Thinkific LMS just by adding a service provider.</em></strong></p><h4>How JWT SSO works in WSO2 Identity Server?</h4><p>Let’s depict the flow using the below diagram by taking LMS as the application you want to implement SSO.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSFigwG4dROmgym3PipzUA.png" /><figcaption>Flow Diagram</figcaption></figure><p><strong>The Login Flow</strong></p><ul><li><strong><em>jwtRP</em></strong> - The name of the relying party configured in the IDP.</li><li><strong><em>return_to</em></strong> - URL to redirect the user after the successful authentication.</li><li><strong><em>error_url</em></strong> - URL to redirect the user in case of an error occurred in LMS when processing the authentication response received from the IDP.</li></ul><p>As usual, once the user clicks on the Login button of LMS, the user will be redirected to WSO2 Identity Server (the IDP) for authentication. When we send a request to the IDP (/identity/jwtsso), apart from the jwtRP query parameter, we can pass return_to and error_url as additional query parameters. Let’s explain how those parameters are handled in the latter part of this article.</p><p>The WSO2 IS accepts the authentication request and validates the Relying Party (Whether the provided Relying Party exists on the IDP), Return URL, and Error URL (Validates against the regex pattern configured on the IDP). If the validation is failed or anything occurred in the middle, the IDP shows an error page. But as the error occurred in the IDP, it will not make a redirection call to the error URL specified in the authentication request instead, an error page in the WSO2 IS will be shown.</p><p>Once the validation is successful, the IDP will redirect the user to the login page if an already authenticated session does not exist on the IDP. After the user is authenticated or if an already authenticated session exists on the IDP, it will generate the JWT token based on the claims configured. The LMS defines the following claims as mandatory.</p><pre>{<br>   &quot;first_name&quot;: &quot;Alex&quot;,<br>   &quot;last_name&quot;: &quot;John&quot;,<br>   &quot;email&quot;: &quot;john@mail.com&quot;<br>}</pre><p>Apart from the claims configured in the Service Provider configuration, the IDP will always include <strong>sub</strong> (Subject), <strong>iat</strong> (Issued At Time), <strong>exp</strong> (Expiration Time) and <strong>jti</strong> (JWT ID) claims in the JWT token as below.</p><pre>{<br>  &quot;sub&quot;: &quot;john&quot;,<br>  &quot;first_name&quot;: &quot;Alex&quot;,<br>  &quot;last_name&quot;: &quot;John&quot;,<br>  &quot;exp&quot;: 1590221973,<br>  &quot;iat&quot;: 1590221853,<br>  &quot;jti&quot;: &quot;49d4868d-29ba-4ffe-bce0-c2aa8c0865e1&quot;,<br>  &quot;email&quot;: &quot;john@mail.com&quot;<br>}</pre><p>The generated JWT token will then be signed using the API key of your application (in this scenario, the API key provided by the LMS) and the signed JWT token will be sent as a query parameter.</p><p>Once the LMS receives the JWT token, it will verify the JWT token based on the signature to confirm whether the JWT token was originally sent by the IDP. After validating the JWT token, it will extract the email claim, identify the user, and let the user sign in to the LMS directly without prompting the login page. If the particular user does not have an account on the LMS, it will let the user sign in to LMS after provisioning the user in the background.</p><p>If the return_to parameter is provided on the authentication request made from LMS, once the JWT token is verified, the LMS will redirect the user to the specified Return to URL. In the same context, if the error_url is provided and if any failures occurred during the JWT token verification process (Validating the JWT Signature, and verifying whether if all the mandatory claims are included in the JWT token), it will redirect the user to the specified error URL.</p><p>Specifically, return_to and error_url parameters are not handled by the IDP except validating those parameters. It implies, the LMS is the one redirect the user to the Return to URL or Error URL after it receives the JWT token as the authentication response from the IDP. If the return_to or error_url are not provided, the LMS will redirect the user to the default pages. On the WSO2 IS, we’ll have to add a regex to validate those parameters considering the security concerns involved in it.</p><p><strong>The Logout Flow</strong></p><p>Once the user clicks on the Logout button, the logout request through <em>/identity/jwtsso/logout</em> will terminate the user session on the IDP and the user will be redirected to the Logout URL configured in the SP configuration.</p><h3>In conclusion,</h3><p>The JWT SSO inbound authenticator is a newly built extension in WSO2 Identity Server which provides the capability of integrating SSO for the applications, which require a JWT token as the source of authentication. In this scenario, the user will be authenticated by the WSO2 Identity Server (The Identity Provider) and it will send the authenticated user details using a JWT token as a query parameter. However, as the JWT token is sent as a query parameter, we should not include any sensitive user attributes on the JWT token. Further, considering the security concerns involved with this process such as the replay attack, WSO2 Identity Server includes additional attributes in the JWT token such as JWT ID (<strong>jti</strong>) and the Expiration Time (<strong>exp)</strong>, which helps to implement the following security measures on the application side.</p><ul><li>The token should be accepted by the application for authentication within the specified time period considering the exp claim.</li><li>The token should only be used once to authenticate the user by invalidating the token using the jti claim.</li></ul><p>Predominantly, to confirm whether the JWT token was originally sent by the IDP, the JWT token is signed using the API key of the application and the application must validate the JWT token against the JWT signature. The default algorithm used to sign the JWT token (JWS Algorithm) is <em>HS256</em> and additionally, it supports <em>HS384</em> and <em>HS512</em>.</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2020/07/jwt-sso-with-wso2-identity-server.html">my blog</a>!</p><h4>Let’s implement SSO for Thinkific LMS with WSO2 Identity Server!</h4><p><a href="https://medium.com/@mifrazmurthaja/integrate-thinkific-lms-with-wso2-identity-server-53017f59bbff">Integrate Thinkific LMS with WSO2 Identity Server</a></p><h4>We can use the same to implement SSO for Zendesk with WSO2 Identity Server!</h4><p><a href="https://medium.com/@mifrazmurthaja/implement-sso-for-zendesk-using-wso2-identity-server-a32148313e5c">Implement SSO for Zendesk using WSO2 Identity Server</a></p><h4>Looking for the source code?</h4><p><a href="https://github.com/wso2-extensions/identity-inbound-auth-jwtsso">GitHub - wso2-extensions/identity-inbound-auth-jwtsso: An Inbound Authenticator based on JWT</a></p><h4>The connector is available at,</h4><p><a href="https://store.wso2.com/store/assets/isconnector/details/25bdf0b9-2584-4306-9872-831eaaebe7cd">IS Connector | WSO2 Store</a></p><h3><strong>References</strong></h3><ul><li><a href="https://jwt.io/introduction/">JWT.IO - JSON Web Tokens Introduction</a></li><li><a href="https://is.docs.wso2.com/en/5.10.0/get-started/single-sign-on-and-identity-federation/">Single Sign-On and Identity Federation - WSO2 Identity Server Documentation</a></li><li><a href="https://is.docs.wso2.com/en/5.10.0/learn/configuring-single-sign-on/">Configuring Single Sign-On - WSO2 Identity Server Documentation</a></li><li><a href="https://support.thinkific.com/hc/en-us/articles/360030718713-SSO-Automatically-Sign-in-From-Your-Own-Website">SSO - Automatically Sign in From Your Own Website</a></li><li><a href="https://support.zendesk.com/hc/en-us/articles/203663816-Enabling-JWT-JSON-Web-Token-single-sign-on">Enabling JWT (JSON Web Token) single sign-on</a></li><li><a href="https://mifraz.murthaja.com/2020/07/jwt-sso-with-wso2-identity-server.html">JWT SSO with WSO2 Identity Server</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf486ffba1bf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WSO2 IS Custom Health Checker for Web App Endpoints]]></title>
            <link>https://mifrazmurthaja.medium.com/wso2-is-custom-health-checker-for-web-app-endpoints-c248d24eb353?source=rss-171d8e0afdf2------2</link>
            <guid isPermaLink="false">https://medium.com/p/c248d24eb353</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[wso2-identity-server]]></category>
            <category><![CDATA[custom]]></category>
            <category><![CDATA[health-check]]></category>
            <category><![CDATA[servers]]></category>
            <dc:creator><![CDATA[Mifraz Murthaja]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 16:52:25 GMT</pubDate>
            <atom:updated>2022-12-12T04:19:12.514Z</atom:updated>
            <content:encoded><![CDATA[<p>In the administration point of view, testing server health is an obligatory requirement. In the same context, WSO2 Identity Server provided built-in <a href="https://is.docs.wso2.com/en/5.9.0/setup/monitoring-server-health/"><strong>Carbon Health Check API</strong></a> which can be used to check the health of WSO2 Identity Server.</p><p>There are three health checkers available by default, which are: Data sources health checker, Server startup health checker, and Super tenant user store health checker. Refer <a href="https://is.docs.wso2.com/en/5.9.0/setup/monitoring-server-health/"><strong>Monitoring Server Health</strong></a> documentation for more details on built-in health checkers. In this blog, will implement a custom health checker which can be deployed on WSO2 IS to test any other web endpoints along with the default health checkers.</p><p><strong>Let’s create a new maven project.</strong></p><pre>mvn archetype:generate -DgroupId=org.wso2.carbon.custom.healthcheck -DartifactId=org.wso2.carbon.healthcheck -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false</pre><p>Once you’ve created the maven project, let’s add the dependencies required and change the project packaging to OSGI bundle.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e433179db319fd926b5f1217d56919db/href">https://medium.com/media/e433179db319fd926b5f1217d56919db/href</a></iframe><p>Let’s override the required methods and implement other necessary methods to test the web application endpoints.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/967430b806d92e4328ce48be824a3a5c/href">https://medium.com/media/967430b806d92e4328ce48be824a3a5c/href</a></iframe><p>Now, we’ll have to implement the BundleActivator to register the OSGI bundle on the WSO2 IS server.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/52b00660f84688dcdc261aa00f2249f1/href">https://medium.com/media/52b00660f84688dcdc261aa00f2249f1/href</a></iframe><p>That’s it! Let’s compile the project.</p><pre>mvn clean install</pre><p>Let’s place the org.wso2.carbon.healthcheck-1.x.x.jar available in the target directory into &lt;IS_HOME&gt;/repository/components/dropins directory of WSO2 IS Server.</p><p>Finally, enable and configure the health checker in the deployment.toml file resides in &lt;IS_HOME&gt;/repository/conf directory as below.</p><pre>[carbon_health_check]<br>enable = true<br><br>[[health_checker]]<br>name = &quot;WebAppHealthChecker&quot;<br>order = &quot;90&quot;<br><br>[health_checker.properties]<br>success_code = 200<br>error_code = &quot;HC_00006&quot;<br>webapps = &quot;https://localhost:9443/carbon/product/about.html, https://localhost:9443/webapp1&quot;</pre><p>The properties used in the custom carbon health check API are explained below.</p><ul><li><strong>success_code</strong> : The return code to be returned to identify if the web applications are up and running.</li><li><strong>error_code</strong> : The error code to be returned if any of the web applications are not deployed/ not running when the carbon health check API is invoked.</li><li><strong>webapps</strong> : The web applications to be checked when the carbon health check API is invoked.</li></ul><p><strong>Let’s invoke the API</strong></p><p>This is an open API that should ideally be blocked at the load balancer level. To invoke it, start the WSO2 product and send a GET request to the health check API. A sample cURL command is shown below.</p><pre>curl -k -v https://localhost:9443/api/health-check/v1.0/health</pre><p>The code block below shows a sample 503 Unavailable response with an array of errors. Please note that the code: HC_00006 is the error code we’ve configured above.</p><pre>{<br>   &quot;errors&quot;:[<br>      {<br>         &quot;code&quot;:&quot;HC_00006&quot;,<br>         &quot;message&quot;:&quot;Error while getting server status&quot;,<br>         &quot;description&quot;:&quot;Web Applications not deployed/ not running : [ https://localhost:9443/webapp1]&quot;<br>      }<br>   ]<br>}</pre><p>Refer to <a href="https://is.docs.wso2.com/en/5.9.0/setup/monitoring-server-health/#adding-new-health-checkers">Monitoring Server Health — 5.9.0 Doc</a> for more details on configuring the Carbon Health Check API for WSO2 IS 5.9.0.</p><p>Folk this project on <a href="https://github.com/mifrazmurthaja/custom-carbon-health-check">GitHub</a>. It also guides on configuring this for the IS versions prior to 5.9.0.</p><p>Find this on <a href="https://mifrazmurthaja.blogspot.com/2020/07/wso2-is-custom-health-checker-for-web-app-endpoints.html">my blog</a>!</p><p><strong>References</strong>:</p><ul><li><a href="https://is.docs.wso2.com/en/5.9.0/setup/monitoring-server-health">Monitoring Server Health - WSO2 Identity Server Documentation</a></li><li><a href="https://docs.wso2.com/display/ADMIN44x/Monitoring+Server+Health">Monitoring Server Health</a></li><li><a href="https://github.com/mifrazmurthaja/custom-carbon-health-check">mifrazmurthaja/custom-carbon-health-check</a></li><li><a href="https://mifraz.murthaja.com/2020/07/wso2-is-custom-health-checker-for-web-app-endpoints.html">WSO2 IS Custom Health Checker for Web App Endpoints</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c248d24eb353" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>