Heya sorry if I'm not getting something, shouldn't this read 2 dots which separate 3 parts?

It's a lot of text as of now. It will be better if we can create a sketch showcasing the flow of info between client <-> identity server : client <-> application server

In Create token page, user should be able to change the algorithm options and get the token accordingly

It started as a tiny project but now the code has grown large for single file. Separate out the views, controllers, helpers and services in different folders and files. The purpose is to improve readability, code reuse and speed up development.

Spotted on angular frontend's /anatomy page.

Likely because of font-grey flex property. Removing that fixes the issue.

At some places, content overflows. Test and fix

Can we put a summary at the start/end that explains JWT more simply in a way that it is memorable?
The challenge is that there are multiple complex concepts that needs to be explained(asymmetric cryptography, signature, authentication, authorization,...).

Use of some visuals may help. Explaining 1 concept at a time may help.

Json code(shown for request/response samples) does not look much readable at the moment. Fix it.

Angular being js based has limitations in seo. Figure out what technical changes we need to make to improve SEO.

• Add robots.txt for api
• Add sitemap.xml for api
• Add meta headers(with canonical url) for SEO in api
• Add sitemap.xml for frontend
• Add robots.txt for frontend
• Add meta headers(with canonical url) for SEO in frontend
• #26

Desktop

Screen 1: https://zpl.io/O0MwxMk
Screen 2: https://zpl.io/ll4wDy5
Screen 3: https://zpl.io/7wz9WRv (Edit state of the JWT)
Screen 4: https://zpl.io/W4rzNPp

Tab (Screen sizes between 768px and 991px)

Screen 1: https://zpl.io/ewdEAXD
Screen 2: https://zpl.io/7wz9WqR
Screen 3: https://zpl.io/3XZ5j31

Mobile (screen sizes less than 768px)

Screen 1: https://zpl.io/g8o4kg1
Screen 2: https://zpl.io/L48l5BM
Screen 3: https://zpl.io/PqOJ94D

For anatomy page

Currently, the project stores only single global choice of signOptions for all the users. This will definitely create unexpected results when multiple users have different choices for signOptions(e.g. signing algorithm).
To fix this, maintain a user vs signOptions list. So each user's preferences are separated.