You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
separate web and mobile examples for redirect uri's (#8196)
* separate web and mobile examples for redirect uri's
* Revert "separate web and mobile examples for redirect uri's"
This reverts commit e6fad5d.
* separate web and mobile examples for redirect uri's
* fix snippets, add email: true
* move rn filter to mobile examples
You need to now inform your external provider of the newly configured authentication resource and its OAuth redirect URI:
154
194
155
195
<BlockSwitcher>
@@ -222,11 +262,14 @@ Learn more about using social identity providers with user pool](https://docs.aw
222
262
223
263
You can determine the pieces of data you want to retrieve from each external provider when setting them up in the `amplify/auth/resource.ts` file using `scopes`.
You can map which attributes are mapped between your external identity provider and your users created in Cognito. We will be able to have the best level of protection for developers if we ensure that attribute mappings that would not work are called out by the type system.
@@ -254,11 +322,14 @@ If you specify an attribute in your authentication resource as required, and it
[Learn more about configuring the React Authenticator component for external providers](https://ui.docs.amplify.aws/react/connected-components/authenticator/configuration#external-providers)
To setup a OIDC provider, you can configure them in your `amplify/auth/resource.ts` file. For example, if you would like to setup a Microsoft EntraID provider, you can do so as follows:
Use the `signInWithRedirect` API to initiate sign-in with an OIDC identity provider.
@@ -330,6 +461,8 @@ await signInWithRedirect({
330
461
331
462
To setup a SAML provider, you can configure them in your `amplify/auth/resource.ts` file. For example, if you would like to setup a Microsoft EntraID provider, you can do so as follows:
Use the `signInWithRedirect` API to initiate sign-in with a SAML identity provider.
@@ -474,7 +634,6 @@ import { signInWithRedirect } from 'aws-amplify/auth';
474
634
signInWithRedirect({
475
635
provider: 'Apple'
476
636
});
477
-
478
637
```
479
638
480
639
### Redirect URLs
@@ -485,7 +644,6 @@ _Sign in_ & _Sign out_ redirect URL(s) are used to redirect end users after the
485
644
If you have multiple sign out redirect URLs configured, you may choose to override the default behavior of selecting a redirect URL and provide the one of your choosing when calling `signOut`. The provided redirect URL should match at least one of the configured redirect URLs. If no redirect URL is provided to `signOut`, the first item from the the configured redirect URLs list that does not contain a HTTP nor HTTPS prefix will be picked.
486
645
487
646
```ts
488
-
import { Amplify } from'aws-amplify';
489
647
import { signOut } from'aws-amplify/auth';
490
648
491
649
// Assuming the following URLS were provided manually or via the Amplify configuration file,
@@ -494,10 +652,9 @@ import { signOut } from 'aws-amplify/auth';
<Callout> Irrespective of whether a `redirectUrl` is provided to `signOut`, a URL that does not contain http or https is expected to be present in the configured redirect URL list. This is because iOS requires an appScheme when creating the web session. </Callout>
0 commit comments