Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mam SDK does not work with Microsoft Authenticator #67

Open
shafersystems opened this issue Aug 2, 2022 · 7 comments
Open

Mam SDK does not work with Microsoft Authenticator #67

shafersystems opened this issue Aug 2, 2022 · 7 comments

Comments

@shafersystems
Copy link

When using MSAL library for authentication and the user has Microsoft Authenticator installed, the Authenticator app is blocked from returning the token to the calling application. This is true even if +msauth.your.application.bundle is added to the list of allowed URL schemes in the application MDX policies.

@jaspreetsingh-citrix
Copy link
Collaborator

Hi Joel,
Back in April, Chetan mentioned this issue and I believe I suggested the exact URL scheme used by the MSAuth app to return to the app, to be added to the "App URL schemes" policy, which it seems (+msauth.your.application.bundle) was already added.
Is it possible to share the logs at the higher log level (maybe 10) to triage further?

@shafersystems
Copy link
Author

shafersystems commented Aug 10, 2022 via email

@jaspreetsingh-citrix
Copy link
Collaborator

jaspreetsingh-citrix commented Aug 10, 2022

Hi @shafersystems.

To collect logs,

  1. Open SecureHub -> Help -> Report Issue -> (Select your app).

  2. This would flip to your app briefly and return to SecureHub. SecureHub would show a draft mail compose view.

  3. Don't type in anything just yet, scroll down to open Advanced log settings,
    3.a. Check what is the Log Level set to. By default, if the log policies were not changed on CEM server for the app, it should be set "Info Messages (4)", but change it to at least Level 10.
    3.b. If the user wants to send the logs through SecureMail if installed, then keep the last open "Send using Citrix SecureMail" enabled, or else disable it.

  4. If 3.a. was not changed, skip to Step5, or else if 3.a. was changed,
    4.a. on going back to draft Report Issue mail to compose view, you would be asked to reproduce the issue. Clicking on Go to button, would flip to the app and there you can reproduce the issue again, which now would start logging with a higher log level.
    4.b. Once reproduced, repeat Steps 1, 2, and 5.

  5. Once back in the Report issue draft mail-compose view, click on Send, this would produce native mail compose view or would flip to SecureMail. This should include a zipped support bundle with the required logs.

@shafersystems
Copy link
Author

shafersystems commented Aug 10, 2022 via email

@jaspreetsingh-citrix
Copy link
Collaborator

Android?

@jaspreetsingh-citrix
Copy link
Collaborator

Hi @shafersystems, I suppose I wasn't clear earlier. Do you see this issue on iOS or Android?

@shafersystems
Copy link
Author

Hi @Jaspreet1, we see this on Android.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants