Migrating to the New SSO Redirect URI for AWS Wickr

Introduction

AWS Wickr has introduced an improved, more secure SSO connection system. To take advantage of these security enhancements, organizations using SSO must migrate to the new redirect URI by March 09, 2026. This upgrade is seamless and won't affect your users' existing SSO connections.

Instructions

• Open the AWS Management Console for Wickr at https://console.aws.amazon.com/wickr/.
• On the Networks page, if you have one or more networks with SSO configured, a banner will notify you that a migration is available.
• Select the Migrate button on the banner to navigate to the redirect URI migration wizard for the network.
• Follow the steps in the migration wizard. Additional details for specific steps are available below:

Step 1

• You will need to add the new redirect URI to your identity provider settings. To do this, first copy the new redirect URI.

• Navigate to the identity provider you are using for the Wickr network, and add the new URI. Important Note: DO NOT remove the current URI yet.

Example: Adding the new URI in Okta

• Follow steps in the AWS Wickr Single Sign-on (SSO) setup with Okta guide to navigate to Sign-in redirect URIs.
• Select Add URI and paste the new redirect URI you had copied.

Example: Adding the new URI in Amazon Cognito

• Follow steps in the AWS Wickr Single Sign-on (SSO) setup with Amazon Cognito guide to navigate to Managed login pages configuration.
• Select Edit then Add another URL and paste the new redirect URI you had copied.

Example: Adding the new URI in Microsoft Entra (Azure AD)

• Follow steps in the Configure AWS Wickr with Microsoft Entra (Azure AD) single sign-on guide to navigate to Redirect URI
• Select Add URI to add an additional Web URI and paste the new redirect URI you had copied.

Step 2

• Select on the link provided in Step 2 of your Wickr admin console's wizard to ensure the URI is accessible on your network. In some cases, this list may take several hours to update.
• You will be able to see the login page when available. Example:

• To confirm the update, attempt to sign in as any user on your network. You should be able to see the Login success screen. Example:

Step 3

• Select Activate in the wizard to activate the new redirect URI.

Step 4

Important DO NOT proceed if you were not able observe Login Successful screen in Step 2, to confirm you were able to login successfully with the new URI.

• As your migration is complete, and new redirect URI is activated, you should remove the previous redirect URI from your identity provider settings. To do this, follow examples in step 1 to navigate to the URI configuration steps, and remove only the old URI: https://messaging-pro-alpha.secmv.net/deeplink/oidc.php. DO NOT remove the new URI.

Step 5

• Select Finalize in the migration wizard to complete the migration.