Ul part two

_source/_posts/2024-04-30-express-universal-logout.md

@@ -732,7 +732,7 @@ export const Todos = () => {
 This web application architecture uses cookie-based sessions instead of session tokens to authenticate to the backend resources. However, in the case of mobile apps and single-page applications, you'll need to revoke refresh tokens on the front end. As per the [spec](https://datatracker.ietf.org/doc/html/draft-parecki-oauth-global-token-revocation#name-revocation-expectations), written by [Aaron Parecki](https://aaronparecki.com/) a successful sign-out will require revoking a user's refresh token. 
 
 ## Initiate Universal Logout through Okta 
-This tutorial provides the fundamental steps to creating a UL endpoint to end a user's session or tokens. UL is currently available [Early Access in Okta Preview orgs](https://help.okta.com/oie/en-us/content/topics/itp/universal-logout.htm). Once generally available a secondary blog will be posted with complete instructions on how to initiate sign-out end-to-end with Okta. Stay tuned! For now, you can find the completed project [ul-workshop-complete](https://github.com/oktadev/okta-enterprise-ready-workshops/tree/ul-workshop-complete) on our Oktadev GitHub repository. 
+This tutorial provides the fundamental steps to creating a UL endpoint to end a user's session or tokens, you can test the a working example here [ul-workshop-complete](https://github.com/oktadev/okta-enterprise-ready-workshops/tree/ul-workshop-complete) on our Oktadev GitHub repository. To connect you integration to Okta you can follow this blog – Universal Logout Part 2 – for more information! 
 
 ## Continue adding more features to your SaaS app!
 Now that you have an OIDC app with a UL endpoint, you can continue your Enterprise-Ready journey by adding user lifecycle management through System for Cross-domain Identity Management [(SCIM)](https://datatracker.ietf.org/doc/html/rfc7644).