Självstudie: Logga in och logga ut från en Enkelsidig JavaScript-app (SPA)

Gäller för: Arbetskraftshyresgäster Externa hyresgäster (läs mer)

Den här självstudien är den sista delen i en serie som visar hur du skapar ett JavaScript-ensidesprogram (SPA) och förbereder det för autentisering med hjälp av Microsofts identitetsplattform. I del 2 i den här serien lade du till autentiseringsflöden i ett JavaScript SPA och skapade ett dynamiskt användargränssnitt. Det här sista steget visar hur du testar inloggnings- och utloggningsfunktioner i din app.

I den här handledningen kommer du att:

• Lägg till kod i claimUtils.js-filen för att skapa anspråkstabellen
• Logga in och logga ut från programmet
• Visa anspråken som returneras från ID-tokenen.

Förutsättningar

• Självstudie: Förbereda ett JavaScript-ensidesprogram för autentisering.

Lägg till kod i claimUtils.js -filen (valfritt)

Om du vill lägga till funktionen i en tabell som kan visa anspråk som returneras från ID-token kan du lägga till kod i claimUtils.js-filen. Det här kodfragmentet fyller i anspråkstabellen med lämplig beskrivning och motsvarande värde.

1. Öppna offentliga/claimUtils.js och lägg till följande kodfragment:

    /**
    * Populate claims table with appropriate description
    * @param {Object} claims ID token claims
    * @returns claimsObject
    */
   const createClaimsTable = (claims) => {
       let claimsObj = {};
       let index = 0;
   
       Object.keys(claims).forEach((key) => {
           if (typeof claims[key] !== 'string' && typeof claims[key] !== 'number') return;
           switch (key) {
               case 'aud':
                   populateClaim(
                       key,
                       claims[key],
                       "Identifies the intended recipient of the token. In ID tokens, the audience is your app's Application ID, assigned to your app in the Entra admin center.",
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'iss':
                   populateClaim(
                       key,
                       claims[key],
                       'Identifies the issuer, or authorization server that constructs and returns the token. It also identifies the Microsoft Entra tenant for which the user was authenticated. If the token was issued by the v2.0 endpoint, the URI will end in /v2.0. The GUID that indicates that the user is a consumer user from a Microsoft account is 9188040d-6c67-4c5b-b112-36a304b66dad.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'iat':
                   populateClaim(
                       key,
                       changeDateFormat(claims[key]),
                       'Issued At indicates when the authentication for this token occurred.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'nbf':
                   populateClaim(
                       key,
                       changeDateFormat(claims[key]),
                       'The nbf (not before) claim identifies the time (as UNIX timestamp) before which the JWT must not be accepted for processing.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'exp':
                   populateClaim(
                       key,
                       changeDateFormat(claims[key]),
                       "The exp (expiration time) claim identifies the expiration time (as UNIX timestamp) on or after which the JWT must not be accepted for processing. It's important to note that in certain circumstances, a resource may reject the token before this time. For example, if a change in authentication is required or a token revocation has been detected.",
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'name':
                   populateClaim(
                       key,
                       claims[key],
                       "The principal about which the token asserts information, such as the user of an application. This value is immutable and can't be reassigned or reused. It can be used to perform authorization checks safely, such as when the token is used to access a resource. By default, the subject claim is populated with the object ID of the user in the directory",
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'preferred_username':
                   populateClaim(
                       key,
                       claims[key],
                       'The primary username that represents the user. It could be an email address, phone number, or a generic username without a specified format. Its value is mutable and might change over time. Since it is mutable, this value must not be used to make authorization decisions. It can be used for username hints, however, and in human-readable UI as a username. The profile scope is required in order to receive this claim.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'nonce':
                   populateClaim(
                       key,
                       claims[key],
                       'The nonce matches the parameter included in the original /authorize request to the IDP. If it does not match, your application should reject the token.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'oid':
                   populateClaim(
                       key,
                       claims[key],
                       'The oid (user’s object id) is the only claim that should be used to uniquely identify a user in an Azure AD tenant. The token might have one or more of the following claim, that might seem like a unique identifier, but is not and should not be used as such.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'tid':
                   populateClaim(
                       key,
                       claims[key],
                       'The tenant ID. You will use this claim to ensure that only users from the current Azure AD tenant can access this app.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'upn':
                   populateClaim(
                       key,
                       claims[key],
                       '(user principal name) – might be unique amongst the active set of users in a tenant but tend to get reassigned to new employees as employees leave the organization and others take their place or might change to reflect a personal change like marriage.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'email':
                   populateClaim(
                       key,
                       claims[key],
                       'Email might be unique amongst the active set of users in a tenant but tend to get reassigned to new employees as employees leave the organization and others take their place.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'acct':
                   populateClaim(
                       key,
                       claims[key],
                       'Available as an optional claim, it lets you know what the type of user (homed, guest) is. For example, for an individual’s access to their data you might not care for this claim, but you would use this along with tenant id (tid) to control access to say a company-wide dashboard to just employees (homed users) and not contractors (guest users).',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'sid':
                   populateClaim(key, claims[key], 'Session ID, used for per-session user sign-out.', index, claimsObj);
                   index++;
                   break;
               case 'sub':
                   populateClaim(
                       key,
                       claims[key],
                       'The sub claim is a pairwise identifier - it is unique to a particular application ID. If a single user signs into two different apps using two different client IDs, those apps will receive two different values for the subject claim.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'ver':
                   populateClaim(
                       key,
                       claims[key],
                       'Version of the token issued by the Microsoft identity platform',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'auth_time':
                   populateClaim(
                       key,
                       claims[key],
                       'The time at which a user last entered credentials, represented in epoch time. There is no discrimination between that authentication being a fresh sign-in, a single sign-on (SSO) session, or another sign-in type.',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'at_hash':
                   populateClaim(
                       key,
                       claims[key],
                       'An access token hash included in an ID token only when the token is issued together with an OAuth 2.0 access token. An access token hash can be used to validate the authenticity of an access token',
                       index,
                       claimsObj
                   );
                   index++;
                   break;
               case 'uti':
               case 'rh':
                   index++;
                   break;
               default:
                   populateClaim(key, claims[key], '', index, claimsObj);
                   index++;
           }
       });
   
       return claimsObj;
   };
   
       /**
        * Populates claim, description, and value into an claimsObject
        * @param {string} claim
        * @param {string} value
        * @param {string} description
        * @param {number} index
        * @param {Object} claimsObject
        */
       const populateClaim = (claim, value, description, index, claimsObject) => {
           let claimsArray = [];
           claimsArray[0] = claim;
           claimsArray[1] = value;
           claimsArray[2] = description;
           claimsObject[index] = claimsArray;
       };
   
       /**
        * Transforms Unix timestamp to date and returns a string value of that date
        * @param {string} date Unix timestamp
        * @returns
        */
       const changeDateFormat = (date) => {
           let dateObj = new Date(date * 1000);
           return `${date} - [${dateObj.toString()}]`;
   };
   

2. Spara filen.

Kör projektet och logga in

Nu när alla nödvändiga kodfragment har lagts till kan programmet anropas och testas i en webbläsare.

1. Öppna en ny terminal och kör följande kommando för att starta expresswebbservern.

   npm start
   

2. Kopiera den http URL som visas i terminalen, till exempel http://localhost:3000och klistra in den i en webbläsare. Vi rekommenderar att du använder en privat eller inkognito-webbläsarsession.

3. Logga in med ett konto som är registrerat hos hyresgästen.

4. Ett gränssnitt som liknar följande skärmbild visas som anger att du har loggat in på programmet. Om du har lagt till anspråkstabellen kan du visa anspråken som returneras från ID-token.

   

Logga ut från programmet

1. Hitta knappen Logga ut på sidan och välj den.
2. Du uppmanas att välja ett konto att logga ut från. Välj det konto som du använde för att logga in.

Ett meddelande visas som anger att du har loggat ut. Nu kan du stänga webbläsarfönstret.

Relaterat innehåll

• Snabbstart: Skydda ett ASP.NET Core-webb-API med Microsofts identitetsplattform.
• Lär dig mer genom att bygga ett React SPA som låter användare logga in i följande självstudiekurs i flera delar.
• Aktivera lösenordsåterställning.
• Anpassa standardvarumärkningen.
• Konfigurera inloggning med Google.