Hi Team,
Would it be possible for the Tulip team to develop user deactivation APIs? Currently, we manually deactivate users on a monthly basis, which is a slow and time-consuming process. Automating this through APIs would improve efficiency and provide more control over user access management.
Please let me know if this can be considered for development.
Thanks.
Hi Jay, quick follow up, when you say “users”, do you mean:
- Users of the online Tulip portal
- Users of the Player (operators)
- Both
Both, and I think it’s same, correct? because there is no different way to deactivate operator vs SSO users?
Here’s the difference with SSO- when a user is deactivated in your IdP, they are no longer able to log in to Tulip. As opposed to normal Tulip authentication, where they must be manually deactivated.
So with SSO, have you found that deactivation of a user in your IdP is successfully translating to deactivation in Tulip? Or are you not able to do that on the IdP side?
Hi Kevin,
Just to clarify, the reason operators can log in using their badge IDs is because their accounts are not currently configured for Single Sign-On (SSO).
@sandeep.ingale
Understood on both points, thank you. Both are currently on our roadmap for 2025.
The part I forgot was that for users of Tulip, when they are deactivated in your IdP, it does not give that feedback to Tulip currently. The user remains “active” in Tulip, even though they can never re-enter the product. The operator part is just on the Tulip side, so it does not have that distinction.
1 Like
Thanks for the update. Is it possible for you to add us in Beta testing? because we would love to use this functionality and test as soon as tulip build it.
Of course! Will follow up when we have news.
1 Like