A Flutter OAuth package for performing user authentication against Azure Active Directory OAuth2 v2.0 endpoint.
Azure Active Directory OAuth #
A Flutter OAuth package for performing user authentication against Azure Active Directory OAuth2 v2.0 endpoint. Forked from hitherejoe.FlutterOAuth.
Afterwards you have to initialize the library as follow:
static final Config config = new Config( tenant: "YOUR_TENANT_ID", clientId: "YOUR_CLIENT_ID", scope: "openid profile offline_access", redirectUri: "your redirect url available in azure portal" ); final AadOAuth oauth = new AadOAuth(config);
This allows you to pass in an tenant ID, client ID, scope and redirect url.
Then once you have an OAuth instance, you can call
login() and afterwards
getAccessToken() to retrieve an access token:
await oauth.login(); String accessToken = await oauth.getAccessToken();
You can also call
getAccessToken() directly. It will automatically login and retrieve an access token.
Tokens are stored in Keychain for iOS or Keystore for Android. To destroy the tokens you can call
B2C Usage #
Setup your B2C directory - Azure AD B2C Setup.
Register an App on the previously created B2C directory - Azure AD B2C App Register.
Use native app as plattform type (with callback URL: https://login.live.com/oauth20_desktop.srf).
Create your user flows - Azure AD B2C User Flows
Add your Azure tenant ID, tenantName, client ID (ID of App), client Secret (Secret of App) and redirectUrl in the main.dart source-code:
static final Config configB2Ca = new Config( tenant: "YOUR_TENANT_NAME", clientId: "YOUR_CLIENT_ID", scope: "YOUR_CLIENT_ID offline_access", redirectUri: "https://login.live.com/oauth20_desktop.srf", clientSecret: "YOUR_CLIENT_SECRET", isB2C: true, policy: "YOUR_USER_FLOW___USER_FLOW_A", tokenIdentifier: "UNIQUE IDENTIFIER A");
Afterwards you can login and get an access token for accessing other resources. You can also use multiple configs at the same time.
Add the following to your pubspec.yaml dependencies:
dependencies: aad_oauth: "^0.2.0"
Contributions can be submitted as pull requests and are highly welcomed. Changes will be bundled together into a release. You can find the next release date and past releases in the CHANGELOG file.