You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New features:
- Minimum length notice for HMAC algorithms, including tooltip.
- Share button
- Easy library edition: libraries are now loaded from JSON files, no HTML or code needs to be edited
- Library tests
- Accept more tokens as URL params (PR)
- Claim info tooltips
- Plain RSA keys (no X509 header) are now supported
Bug fixes:
- Correct font
- Minor positioning fixes
- Added missing star counts
Libraries:
- More libraries
- Updated libraries
To add a library, simply edit the right JSON file located at `views/website/libraries`. Each language gets its own file. Multiple libraries share the same language file.
9
+
10
+
To add a new language, simply add a JSON file in the same folder as the others. It will get automatically recognized. If you add a new language, you will need to provide a proper icon for it and place it in the `img` folder.
11
+
12
+
Here's a commented example of the .NET language file (`0-.NET.json`). All fields must have valid values unless noted:
13
+
14
+
```javascript
15
+
{
16
+
// Language name (unique)
17
+
"name":".NET",
18
+
19
+
// Unique identifier that will be used as a CSS class
20
+
// for this language (only valid CSS class names).
21
+
"uniqueClass":"net",
22
+
23
+
// The language icon, SVG format preferred, should be placed
24
+
// in /img directory.
25
+
"image":"/img/1.svg",
26
+
27
+
// The color of header that displays the name of the language
28
+
// and the icon. This is a valid CSS color definition.
29
+
"bgColor":"rgb(42, 168, 229)",
30
+
31
+
// An array of libraries for this language.
32
+
"libs": [
33
+
{
34
+
// In case the library suffered from a vulnerability, the
35
+
// minimum version in which the vuln was fixed must be
36
+
// listed here. Optional (can be null).
37
+
"minimumVersion":"1.0.1", // or null
38
+
39
+
// Supported features, true for supported,
40
+
// false for not supported.
41
+
"support": {
42
+
"sign":true,
43
+
"verify":true,
44
+
"iss":true,
45
+
"sub":true,
46
+
"aud":true,
47
+
"exp":true,
48
+
"nbf":true,
49
+
"iat":true,
50
+
"jti":true,
51
+
"hs256":true,
52
+
"hs384":true,
53
+
"hs512":true,
54
+
"rs256":true,
55
+
"rs384":true,
56
+
"rs512":true,
57
+
"es256":true,
58
+
"es384":true,
59
+
"es512":true
60
+
},
61
+
62
+
// Author URL, can be GitHub profile, personal page
63
+
// company page, etc. Can be null.
64
+
"authorUrl":"https://www.microsoft.com", // or null
65
+
66
+
// Author name.
67
+
"authorName":"Microsoft",
68
+
69
+
// For the star count, this is the GitHub repository path,
70
+
// (usually user/repo). Can be null (no star count shown).
71
+
"gitHubRepoPath":"AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet", // or null
You will find the generated files in the `dist` directory. For the website, you can run a server at its root. For example: `http-server dist/website`.
97
+
You will find the generated files in the `dist` directory. For the website, you can run a server at its root. For example: `http-server dist/website`. The default `grunt` task runs a server
98
+
at [https://127.0.0.1:8000](https://127.0.0.1:8000) and watches
99
+
for changes.
22
100
23
-
### Happy hacking!
101
+
To run tests, execute:
24
102
103
+
```
104
+
./node_modules/.bin/grunt test
105
+
```
25
106
107
+
Look at the end of the `Gruntfile` for other common tasks.
0 commit comments