Symptoms

Customer is receiving an issue where the URM service Group method FindUserGroups is retrieving the Group-description name and not the Group-Name.

 

Diagnoses

Its important to remember that the UMUser / UMGroup / UMLabel and UMRole was designed to be generic across all the different security providers (AD, AAD, SP, Salesforce, ADFS, SQLUM and any custom security providers), we thus return the only values that should stay static across all of these security providers, namely Name and Description, any other custom fields will not be recognized and will be ignored.

I have discussed this with our development team and development manager and its important to remember that all Security Providers will be affected with this change and will require analysis from Product Management to determine how to design and implement this change, and a thorough testing cycle will be required to make sure that no other Security Providers are affected.
Even then, existing solutions of other customer is already designed around only the provided columns, and will affect them.
For the feature request route, the best would probably be to add a new method, so as to not affect the existing method.

Alternatives that we also discussed will be:
1. After receiving the information from the UMGroup SmartObject, execute an additional SmartObject to return the NOGROUP property
2. Expose the assembly using the Endpoint Assembly ServiceInstance and execute the SmartObjects directly.
3. If you do not require the CDGROUP and/or DSGROUP properties then map the NOGROUP to either the Name or Description properties.
4. Create a new custom smartObject, that invokes the methods of the security provider that returns all the required properties
 

Resolution


As the code has been created to only return the Name and Description properties, this is not a K2 product bug and any change in this code will be a change in behaviour, this is why a Feature has already been logged, but has to follow the feature request