Changes for page 1. Authorization

Last modified by Giorgi Mdivnishvili on 2024/04/26 15:59

From version 30.1
edited by Giorgi Mdivnishvili
on 2024/04/11 15:34
Change comment: There is no comment for this version
To version 35.1
edited by Giorgi Mdivnishvili
on 2024/04/26 15:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -42,12 +42,20 @@
42 42  
43 43  {{code language="Json"}}
44 44  {
45 - "accessToken": "string"
45 + "accessToken": "string",
46 + "refreshToken": "string",
47 + "passwordExpired": true
46 46  }
47 47  {{/code}}
48 48  
49 49  
52 +expiration time 30 days for both tokens:
50 50  
54 +accessToken - 43200 min
55 +
56 +refreshToken - 2591968 sec
57 +
58 +
51 51  === Schema ===
52 52  
53 53  (% data-xwiki-non-generated-content="java.util.List" %)
... ... @@ -56,32 +56,77 @@
56 56  )))
57 57  
58 58  {{success}}
59 -AuthRequest{
67 +AuthResponse{
60 60  
61 -|login|string
69 +|accessToken|string
62 62  nullable: true
63 -|password|string
71 +|refreshToken|string
64 64  nullable: true
73 +|passwordExpired|boolean
65 65  
66 66  }
67 67  {{/success}}
68 68  
69 69  
70 -== Important ==
71 71  
72 -{{error}}
73 -It's Important to in every other request header, put Auth token
74 74  
75 -**Key **- Authorization
81 += RefreshToken =
76 76  
77 -**Value **- Bearer Token what is given in this response. (Authorization type Bearer Token)
78 78  
84 +To retrieve an existing accesstoken , you can  make a request for the given endpoint below and pass in the body refreshToken, after that you will receive an accessToken. You can use this method at your discretion.
79 79  
80 -**also note in headers that:**
81 81  
82 -Content-Type - application/json
87 +== Request URL - [POST] ==
83 83  
84 -**Key - **X-nugios-timezone
89 +(% class="box infomessage" %)
90 +(((
91 +[[https:~~/~~/integration.kazunion.com/api/Auth/RefreshToken>>https://integration.kazunion.com/api/Auth/RefreshToken]]
92 +)))
85 85  
86 -**Value **- 240
94 +
95 +== Request Parameters ==
96 +
97 +(% class="box" %)
98 +(((
99 +none
100 +)))
101 +
102 +
103 +== (% id="cke_bm_5539S" style="display:none" %) (%%)Request Body example ==
104 +
105 +{{code language="Json"}}
106 +{
107 + "refreshToken": "string"
108 +}
109 +{{/code}}
110 +
111 +
112 +== (% id="cke_bm_11208S" style="display:none" %) (%%)Response Body ==
113 +
114 +{{code language="Json"}}
115 +{
116 + "accessToken": "string",
117 + "refreshToken": "string",
118 + "passwordExpired": true
119 +}
120 +{{/code}}
121 +
122 +
123 +== Important ==
124 +
125 +{{error}}
126 +=== Implementing Authorization in Subsequent Requests ===
127 +
128 +For every API request after the initial authentication, it's crucial to include the authorization token in the request header. This ensures your requests are authorized and can access the necessary resources. Here's how to properly include your token:
129 +
130 +* **Header Key:** Authorization
131 +* **Header Value:** Bearer [Your Token Here] - Use the bearer token provided in the initial authentication response. The authorization type should be specified as Bearer Token.
132 +
133 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
134 +
135 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
136 +* **Header Key:** X-nugios-timezone
137 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
138 +
139 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
87 87  {{/error}}