Changes for page 1. Authorization

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

From version 25.1
edited by Giorgi Mdivnishvili
on 2024/01/09 07:12
Change comment: There is no comment for this version
To version 34.1
edited by Giorgi Mdivnishvili
on 2024/04/26 15:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,9 +7,9 @@
7 7  {{toc/}}
8 8  {{/box}}
9 9  
10 -= Method Description =
10 += Authorization: Starting Your Integration =
11 11  
12 -The initial method of the integration process is authorization. You will be provided with a  unique user username and password to generate the access token that you will need to pass in all the following methods.
12 +The first step in integrating with our API is the authorization process. As a developer, you'll be assigned a unique username and password. These credentials are essential for generating the access token, a critical component that must be included in the headers of all subsequent API requests. This token validates your requests and grants you access to the full suite of our services.
13 13  
14 14  
15 15  == Request URL - [POST] ==
... ... @@ -42,52 +42,104 @@
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:
53 +
54 +accessToken - 43200 min
55 +
56 +refreshToken - 2591968 sec
57 +
58 +
50 50  === Schema ===
51 51  
52 52  (% data-xwiki-non-generated-content="java.util.List" %)
53 53  (((
54 -" class="xwiki-metadata-container">AuthRequest{
63 +
64 +)))
55 55  
56 -|login|string
66 +{{success}}
67 +AuthResponse{
68 +
69 +|accessToken|string
57 57  nullable: true
58 -|password|string
71 +|refreshToken|string
59 59  nullable: true
73 +|passwordExpired|boolean
60 60  
61 61  }
76 +{{/success}}
77 +
78 +
79 +
80 +
81 +
82 +
83 += RefreshToken =
84 +
85 +
86 +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.
87 +
88 +
89 +== Request URL - [POST] ==
90 +
91 +(% class="box infomessage" %)
92 +(((
93 +[[https:~~/~~/integration.kazunion.com/api/Auth/RefreshToken>>https://integration.kazunion.com/api/Auth/RefreshToken]]
62 62  )))
63 63  
64 -{{success}}
65 -AuthRequest{
66 66  
67 -|login|string
68 -nullable: true
69 -|password|string
70 -nullable: true
97 +== Request Parameters ==
71 71  
99 +(% class="box" %)
100 +(((
101 +none
102 +)))
103 +
104 +== ==
105 +
106 +== (% id="cke_bm_5539S" style="display:none" %) (%%)Request Body example ==
107 +
108 +{{code language="Json"}}
109 +{
110 + "refreshToken": "string"
72 72  }
73 -{{/success}}
112 +{{/code}}
74 74  
75 75  
76 -== Important ==
115 +== (% id="cke_bm_11208S" style="display:none" %) (%%)Response Body ==
77 77  
78 -{{error}}
79 -It's Important to in every other request header, put Auth token
117 +{{code language="Json"}}
118 +{
119 + "accessToken": "string",
120 + "refreshToken": "string",
121 + "passwordExpired": true
122 +}
123 +{{/code}}
80 80  
81 -**Key **- Authorization
82 82  
83 -**Value **- Bearer Token what is given in this response.
126 +== ==
84 84  
128 +== Important ==
85 85  
86 -**also note in headers that:**
130 +{{error}}
131 +=== Implementing Authorization in Subsequent Requests ===
87 87  
88 -Content-Type application/json
133 +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:
89 89  
90 -**Key - **X-nugios-timezone
135 +* **Header Key:** Authorization
136 +* **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.
91 91  
92 -**Value **- 240
138 +Additionally, to ensure your requests are properly formatted and recognized, include the following headers:
139 +
140 +* **Content-Type:** Specify this header as application/json to indicate the format of the request body.
141 +* **Header Key:** X-nugios-timezone
142 +* **Header Value:** 240 - Adjust this value to match your local timezone offset in minutes.
143 +
144 +Incorporating these headers with their respective values is essential for the successful processing of your API requests.
93 93  {{/error}}