App Portal seems to show blanks for the User/Group names under the admin security and catalog permissions tabs. The permissions are still being applied as expected. Any idea why App Portal would show a blank for user and groups? It makes it difficult to manage the users and groups if they cannot be identified in the portal.
‎Aug 13, 2024 05:31 AM
Turns out the issue was related to a domain added to the unique username that was not in the list of AD forests. We added a mapping for the domain and that fixed the issue. Once that was added then the groups show as expected.
Thanks CharlesW
‎Aug 21, 2024 08:16 AM
Try running the following query against the App Broker DB:
update WD_AppSettings
set value = 'True'
where keyname = 'HasUntrustedDomains'
After doing this, perform an iisreset.. This tells App Broker to use a different set of calls into AD, which often times resolves this type of issue.
Thanks,
Charles
‎Aug 13, 2024 07:24 AM
I was also going to suggest HasUntrustedDomains. Please note that even in normal operations (assuming you resolve the issue) you may see blanks for some users/groups and not others. This is generally an indication that those users/groups are no longer valid in AD.
‎Aug 13, 2024 09:59 AM
The HasUntrustedDomains is already set to true. And the users/groups are definitely valid and active in AD. The issue still persists.
‎Aug 13, 2024 10:01 AM
I see that you have a support case open for this, and a call is scheduled for tomorrow to discuss. I'll join this call.. Prior to this, if you could enable verbose logging, reproduce the issue, and then upload a set of verbose logs, that may be helpful.
P.S. Interesting that the issue does not happen if you disable SSO.. Makes me think that perhaps the logged in user is getting looked up incorrectly, possibly due to the data in the SSO response.. If the Dev environment is working, with SSO enabled, I don't think that it is directly related to SSO itself.
‎Aug 14, 2024 07:44 AM
Turns out the issue was related to a domain added to the unique username that was not in the list of AD forests. We added a mapping for the domain and that fixed the issue. Once that was added then the groups show as expected.
Thanks CharlesW
‎Aug 21, 2024 08:16 AM