Hello,
I have a IT user that belongs to a Lifetime Team with "change and deploy" permissions, that is not able to assign the team that he belongs to when creating or changing a feature toggle.
On the input field "Teams" he doesn't see any of the teams que belongs to, actually he doesn't see any team.
In the same way, when he tries to search and see/edit a feature toggle, he can not find and see the feature toggles that have the teams restriction.
This issue is only happening to a small group of IT Users.
Any one with the same issue?
Any clue for this behaviour?
Thanks,
Miguel Oliveira
Hi Miguel,
Thank you for reaching out. The information provided is not enough to give you a straight forward solution, but the query (aggregate) being done to retrieve non admin user teams it's available in the following module and path: "FeatureToggle_Mng" - Mainflow > FeatureToggleDetail > GetTeamsWithOrWithoutFeatureToggleTeams > GetTeamsWithOrWithoutFeatureToggleTeams2.
Kindly check why the aggregate it's not retrieving that specific user teams.
Hope it helps.
Cheers -
Alex
Hello Alexandre,
I think already found out what the problem is!
The FeatureToggleTeams_Sync timer that synchronizes teams and roles using the LifeTimeServices/TeamManagementService.asmx web service is failing with the error: “Invalid credentials provided in WS call. Invalid username or password.”
This error occurs because we have IT Users authentication in Lifetime through the OpenID feature with Azure AD and before that we had the SAML plugin.
All the users that have this issue are the ones that were created after we changed the authentication method in Lifetime.
I believe, the Feature Toggle plugin needs to be changed to use LifeTime Services API Token authentication instead of username and password.
Indeed you're right, on FT Management we are still using Lifetime Service API which uses a standard IT User account (login and password), this happens because the LifeTime API v2 it's only available from the platform version 11.16.0 onwards.
In your case, if you're using the platform version 11.16.0 or above it's advisable to custom the FT Management to use the Lifetime API v2, and use a LT Service Account for the API authentication purposes.
We will improve the component to add the capability of using the LifeTime API v2 but it can take a while.
Thank you for your feedback -