{"id":337,"date":"2019-04-05T10:56:37","date_gmt":"2019-04-05T10:56:37","guid":{"rendered":"http:\/\/172.23.1.43\/?p=337"},"modified":"2022-06-07T22:26:13","modified_gmt":"2022-06-07T22:26:13","slug":"mobile-sso-ios-and-bundle-id-the-wildcard-option","status":"publish","type":"post","link":"https:\/\/blog.n-dol.org\/2019\/04\/05\/mobile-sso-ios-and-bundle-id-the-wildcard-option\/","title":{"rendered":"Mobile SSO iOS and Bundle ID: the Wildcard option"},"content":{"rendered":"\n
When we configure Mobile SSO on iOS with VMware Identity Manager, the documentation indicate that, you have to list the applications bundle IDs that will do Mobile SSO, however sometime it can be cumbersome to every single one of them.<\/p>\n\n\n\n\n\n\n\n
Mobile SSO on iOS with IDM rely on the Single Sign-On payload on iOS which allow the usage of wildcard, with the following rules :<\/p>\n\n\n\n
The wildcard character must appear after a period character (.) , and may appear only once, at the end of the string(com.mycompany.*, for example). When a wildcard is included, any app whose bundle ID begins with the prefix is granted access to the account.<\/p><\/blockquote>\n\n\n\n
The only drawback with this is configuration is you won’t have full control over exactly which app. However, using it on internal application will help deployment and make sure that the new internal app is able to use this authentication method without any further configuration from the Workspace ONE Administrator.<\/p>\n\n\n\n
This can be useful for POC and testing purposes as well.<\/p>\n\n\n\n