This lab shows how to use Guest Issuer and Webex Teams Widgets to generate a conversation between a persistent guest account and your Teams user.

The code in this step generates a JSON Web Token and writes it to the console. No useful work happens here, but this demonstrates how a JWT token is created. Future steps will use the token to authenticate a guest account with Webex Teams.

From your Node project, install jsonwebtoken by typing npm install jsonwebtoken

Update index.js to set a display name, a unique user ID, and your Guest Issuer ID on lines 4-6. The display name would correspond to how the user should appear to people they are talking to in Teams. The unique ID goes in the sub field and needs to be unique to this application. Teams guest accounts can be persistent, and you manage the user identity across sessions. The sub field is how you tie a Teams guest to your user's identity. Every session with the same sub field will correspond to the same user. The Guest Issuer ID is supplied by the Webex for Developers portal when you create your Guest application.

On line 11, change the shared secret to match the Shared Secret that was shown when you created the Guest application on Webex for Developers.

Run your app (node index.js) and you'll see the JWT token printed to the screen. It will look something like this:

eyJhbGciOiJIUIwerAgownnR5cCI6IkpXVCJ9.eyJzdWIiOiI5MTY2MDAyNDk3IiwibmFtZSI6IkIiOiI5MTY2MDAyNDk3IiwiselkyOXpjR0ZIiOiI5MTY2MDAyNDk3IiwiT1NWcEJWRWxQVGk5bU1HRm1aVE0wTnkxak1tSmtMVFJsTURZdFlUWTRaaTB6WVdRNU1tSmlPVFUzTXpZIiwiaWF0IjoxNTM5ODE1MzUzLCJleHAiOjE1Mzk4MTg5NTN9.g3-iseeRaNI8LAyoizGcNI8LAGoIgFkiNI8LA0Eotsc

This step will exchange that JWT token for a Webex for Developer Oauth token. The Oauth token can be used with the Webex API like any other Oauth token. The exception is that a Guest oAuth token can only talk to registered Teams users, and cannot talk to other Guests. The oauth token isn't used for anything in this step, just printed to the screen. A later step will use the token to generate a Widget talking to you in Teams.

Install Request (npm install request).

Edit index-2.js to have the same changes as you did in Step 1.

The code from lines 16-26 takes the JWT token and sends it as a POST to the Webex API server, which validates the token and returns an oAuth token. The oAuth token then appears on the screen.

Run the application (node index-2.js) and verify that an oAuth token is logged.

Install express (npm install express).

Edit index-3.js to have the same changes you did in Step 1.

The code from lines 30-34 writes HTML for a Teams widget. Edit line 34 to have the email address you use for your Teams account. The other changes in this file adds a web server at port 5533 using Express, and sets up a route for the root document on that port. Open your browser to http://localhost:5533 and a Teams widget will appear. The User of this Teams widget is your Guest account, and the widget is direct message conversation between the Guest account and your Teams user account.

Send a message from the Widget, and then open Teams with your own account to see that the message arrived. Reply to the message and then return to the widget to see the reply appear there.

Terminate the node app (^C in the console) and restart it (node index-3.js). Reload your browser. Because the guest conversations are persistent, you'll see that the previous conversation remains in the widget.

Now change the sub on line 10 to some other value. Terminate and restart the node application. Reload your browser, and now you'll see that the conversation is empty. This is because the sub is the identifier for Guest user, and so with a new sub, Teams considers this as a new user.

Create a new Guest Issuer application. Use the new Issuer ID and Shared Secret with the same sub and name. See that this is a different conversation, as Teams recognizes the combination of sub and Issuer ID as unique. Two different Issuer IDs can have the same Sub, without it being the same conversation. This means that the sub only needs to be unique within your application, and not unique globally.

Keeping the same sub and Issuer ID, change the name in the Payload. See if this is the same Guest or a different Guest.