As part of the upcoming TFNRegistry™ migration to Somos® Hub, we’re introducing a more streamlined and secure way to access and manage your services. This transition is designed to simplify authentication, improve consistency across tools and create a more efficient experience for your team.
To help TFNRegistry API and WSI users prepare, Somos recently hosted a moderated webinar led by Judy Klein, Senior Director, Product Management, with technical experts Sudhakar Donepudy, Sr. Manager, Software Engineering and Pawan Tripathi, Sr. Software Architect. The main message was straightforward: TFNRegistry API functionality is not changing. What is changing for some users is how access tokens are obtained and how passwords are managed as access moves to Somos Hub.
Key Takeaways
- No functional changes to TFNRegistry APIs or endpoints
- All users must set up access to Somos Hub and enable multi-factor authentication (MFA) after migration launches
- API Key users: no changes expected, but must have a Somos Hub account
- Open Session users: switch to using your Somos Hub password to obtain tokens
- Change Password API is being retired, so password changes move to Somos Hub
- It is imperative users confirm each account has a unique individual email address, not a shared distribution list
- A two-month transition window is planned during production migration, after which, when the Production Launch is complete, all Resp Orgs will access the TFNRegistry using the Somos Hub
Timeline
- Q3 2026: Industry beta
- Early 2027: Production migration begins with a two-month transition window
What specifically is changing for REST API users?
The functional REST APIs are not changing. What’s changing is how some users authenticate to obtain the access token needed to call those APIs. In other words, day-to-day actions like search, reserve and activate remain the same, but the authentication mechanism used to get a token will be updated for users who rely on password-based Open Session.
Why is a Somos Hub account becoming a requirement for all users?
The Somos Hub provides a unified login experience across Somos solutions and establishes a stronger security baseline by enforcing MFA and stronger password policies platform-wide. TFNRegistry will be accessed via Somos Hub, and existing TFNRegistry IDs will be linked to single Somos Hub identity so users will not lose their TFNRegistry IDs during the transition.
How does this impact users with multiple TFNRegistry IDs?
Your individual email address becomes the primary identity in Somos Hub, so it’s important that each user’s email address is unique and not a shared distribution list. During migration, TFNRegistry Login IDs associated to the same email will be linked under one Somos Hub identity and share a single password, which is why ensuring email accuracy and uniqueness ahead of time is a key readiness step.
How will authentication work going forward compared to today?
Token-based authentication continues, and users can still obtain access tokens in one of two ways: via API Keys or via Open Session using Login ID and password. If you use API Keys, your integration will continue to work as-is. If you use Open Session, the main change is that you will use your Somos Hub password instead of your TFNRegistry password when requesting the token. The token you receive works the same way it does today.
What if you rely on Open Session today?
Somos understands that many teams are built around Open Session and that approach will still work, but users will need to plan for the credential change. The speakers also noted there will be a two-month transition period during production migration when Open Session users can use either their existing TFNRegistry password or their new Somos Hub password, giving teams time to switch to ensure no disruption is encountered after the close of the Production Launch.
What is happening to the Change Password API?
The Change Password API is being retired and will no longer be available after the TFNRegistry to Somos Hub transition period ends. If you continue using password-based authentication, password changes will be handled directly in Somos Hub with MFA enabled rather than programmatically via API. This shift supports stronger security practices and reduces the risk associated with password-based automation.
What changes should WSI users expect?
WSI functionality is not changing, and the primary change is the credential used for authentication. Going forward, WSI users will authenticate with Somos Hub credentials. During the two-month transition window, existing passwords will still be accepted to help teams complete the move. In lieu of continuing to use WSI, Somos recommended users explore moving to REST APIs.
If you have not explored REST APIs yet, what should you be doing now?
Somos recommends reviewing the latest REST API specifications on developer.somos.com and comparing them to current WSI use cases since functional parity has been expanded. Teams that need help mapping WSI calls to REST API calls can contact the Somos Help Desk for support.
What are the benefits of moving to API Keys beyond security?
API Keys are a standard approach for machine-to-machine authentication and provide practical operational advantages. They help separate human users from automated systems for cleaner auditing, support easier reversal and rotation if a Key is compromised and enable multiple concurrent sessions, which can simplify parallel automation workflows and integrations.
What is the most common misconception about the transition?
The speakers expect some teams to assume the migration is a large, disruptive integration change. The webinar clarified that endpoints and business logic do not change. For many teams, the practical update is limited to how credentials are managed, particularly for users relying on Open Session and passwords.
What key takeaways should API users be aware of today?
The team reinforced three essentials for the upcoming launch of TFNRegistry to Somos Hub migration:
The team reinforced necessary steps for the upcoming TFNRegistry to Somos Hub migration launch:
- Plan your authentication approach
- Setup your Somos hub account after the migration period launches
- Enable MFA during the migration period
API Key users are not required to make any changes. Open Session users will need to be prepared to use their Somos Hub password. And as a reminder, the Change Password API is going away with password management moving into the Somos Hub.
What To Do Now
- Ensure each user has a unique, individual email address tied to their TFNRegistry login IDs
- Create your Somos Hub account and enable MFA after the migration launches
- Confirm whether your integration uses API Keys or Open Session. If you are using Open Session, investigate moving to API Keys
- If you use Open Session, plan to update your integration to use your Somos Hub password during the transition window
- If you manage passwords programmatically today, plan for that process to change, since the Change Password API is being retired.