We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ts:
var config:LoginOptions = { clientId: 'xxxxx-xxxxx-xxxxx-xxxxx-xxxxx', brokerRedirectUriRegistered: true, keyHash: 'xxxxxxxxxxxxxxxxxxxx', scopes: ['xxxx'], domainHint: "xxxx.xx", tenant: 'xxxxx-xxxxx-xxxxx-xxxxx-xxxxx', authorityType: 'AAD' } const result = await MsAuthPlugin.login(config);
Info.plist:
<key>CFBundleURLTypes</key> <array> <dict> <key>CFBundleURLName</key> <string>com.getcapacitor.capacitor</string> <key>CFBundleURLSchemes</key> <array> <string>msauth.xxx.xxxxx.xxxxx.xxxxx</string> </array> </dict> </array> <key>CFBundleVersion</key> <string>$(CURRENT_PROJECT_VERSION)</string> <key>LSApplicationQueriesSchemes</key> <array> <string>msauthv2</string> <string>msauthv3</string> </array>
registered app registry in azure like msauth://xxx.xxxxx.xxxxx.xxxxx/
Expected behavior: wanted to open the MS Authenticator broker popup
Current behaviour: opening browser modal in ios and redirecting to chrome in android. Q1: Does "@recognizegroup/capacitor-plugin-msauth" support msal broker authentication?
Q2: if yes to Q1, what am i doing / possibly wrong here? Thanks in advance.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ts:
Info.plist:
registered app registry in azure like msauth://xxx.xxxxx.xxxxx.xxxxx/
Expected behavior: wanted to open the MS Authenticator broker popup
Current behaviour: opening browser modal in ios and redirecting to chrome in android.
Q1: Does "@recognizegroup/capacitor-plugin-msauth" support msal broker authentication?
Q2: if yes to Q1, what am i doing / possibly wrong here?
Thanks in advance.
The text was updated successfully, but these errors were encountered: