@@ -7,58 +7,36 @@ import { Step, Steps } from "fumadocs-ui/components/steps";
77
88## Resources
99
10- <Steps >
11- <Step >
12-
13- ### [ Resource Initialization] ( /architectural-resource/resource-initialization )
14-
15- On startup of the Shield server, the resource initialization process is triggered.
16-
17- </Step >
18- <Step >
19-
20- ### [ Admin Login] ( /architectural-resource/admin-login )
21-
22- Once the will reach healthy state then Admin Login api can be used for creation of the API Key.
23-
24- </Step >
25- <Step >
26-
27- ### [ Create API User] ( /architectural-resource/create-api-user )
28-
29- For any client related operations Like login, logout, password reset, etc. the
30- API user is required. There can be more than one API user for a client and each
31- API user can have different role.
32-
33- </Step >
34- <Step >
35-
36- ### [ Signup user] ( /architectural-resource/signup-user )
37-
38- An API user can create or register a new user to its own client.
39-
40- </Step >
41- <Step >
42-
43- ### [ Non Admin Login] ( /architectural-resource/non-admin-login )
44-
45- Regular (Non Admin) user can login to the client at this API endpoint.
46-
47- </Step >
48- <Step >
49-
50- ### [ Refresh Token] ( /architectural-resource/refresh-token )
51-
52- Refresh token is used to refresh the session and generate a new set of token
53- so that the user can continue to use the client without having to login again.
54-
55- </Step >
56- <Step >
57-
58- ### [ Introspection] ( /architectural-resource/introspection )
59-
60- Introspection is used to get the current state of the token. Currently, we
61- support only the access_token introspection.
62-
63- </Step >
64- </Steps >
10+ <Cards >
11+ <Card
12+ title = " Resource Initialization"
13+ href = " /architectural-resource/resource-initialization"
14+ >
15+ On startup of the Shield server, the resource initialization process is
16+ triggered.
17+ </Card >
18+ <Card title = " Admin Login" href = " /architectural-resource/admin-login" >
19+ Once the will reach healthy state then Admin Login api can be used for
20+ creation of the API Key.
21+ </Card >
22+ <Card title = " Create API User" href = " /architectural-resource/create-api-user" >
23+ For any client related operations Like login, logout, password reset, etc.
24+ the API user is required. There can be more than one API user for a client
25+ and each API user can have different role.
26+ </Card >
27+ <Card title = " Signup user" href = " /architectural-resource/signup-user" >
28+ An API user can create or register a new user to its own client.
29+ </Card >
30+ <Card title = " Non Admin Login" href = " /architectural-resource/non-admin-login" >
31+ Regular (Non Admin) user can login to the client at this API endpoint.
32+ </Card >
33+ <Card title = " Refresh Token" href = " /architectural-resource/refresh-token" >
34+ Refresh token is used to refresh the session and generate a new set of token
35+ so that the user can continue to use the client without having to login
36+ again.
37+ </Card >
38+ <Card title = " Introspection" href = " /architectural-resource/introspection" >
39+ Introspection is used to get the current state of the token. Currently, we
40+ support only the access_token introspection.
41+ </Card >
42+ </Cards >
0 commit comments