PKCE

Use Authorization Code with PKCE for user sign-in when developing a browser application locally with MUI Boilerplate. Start here when preparing your local web UI; this page explains the identity setup to arrange with your WEDA support team before following the full MUI sign-in procedure.

The browser signs in as a user. Its public identity client has no client secret and is separate from the Client Credentials used for programmatic integrations.

When to Use It

• Local MUI development: npm run dev on http://localhost:9001 uses the registered public client for Authorization Code with PKCE.
• Deployed MUI build: Uses Portal shared-cookie login. The local PKCE settings do not select the deployed login mode.

Prepare Your Environment

Before configuring the application, prepare:

• WEDA backend origin: The environment your local application will call.
• User account: An account in the same identity environment.
• Public client registration: A client ID with the callback and logout URLs registered for your local application.
• Token exchange compatibility: Confirmation that the WEDA backend accepts the Identity access token for its user-token exchange.

Note: Need help with setup?

Contact the WEDA support team or partner you work with to arrange identity client registration and confirm the environment settings.

Use MUI Boilerplate: Authentication Integration for the exact registration values, environment variables and sign-in steps.

Check the result: You have the registered client ID, matching callback URLs and compatible backend settings needed to follow the local sign-in guide. Client registration alone does not grant access to an organization's resources.