Authentication

Start with the task you want to perform, then follow the matching guide. User Authentication and PKCE both sign in as a user; Client Credentials provides a token for supported programmatic integrations.

Choose a Guide

When you want to...	Start here	How access is obtained
Work in WEDA Console or call WEDA APIs using your user account	User Authentication	Sign in, establish a session, then exchange the session Cookie for a WEDA API access token. Console handles this exchange as part of login.
Send data to a Custom Device over its HTTP ingestion endpoint without an interactive user sign-in	Client Credentials	Exchange a client ID and secret at Identity for an M2M access token with the ingestion audience and scope.
Develop and sign in to a local browser application using MUI Boilerplate	PKCE	Use a registered public identity client for Authorization Code with PKCE, then exchange the Identity access token for a WEDA token.

Creating or managing a Client Credential still uses a user access token. The integration uses the resulting credential to obtain its M2M token. The Client Credentials guide explains both steps and the requirements for Custom Device HTTP ingestion.