Authentication interface one (login callback method)

Interface description

Interface path: /api/authorize.do

HTTP method: GET

HTTP request method

GET

URL parameters

Parameter name Comment (description) response_type must be code (required) string client_id developer's id (required) string redirect_uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response_type=code&client_id=xxxxx&redirect_uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect_uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login-free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula)

Call instructions

• Before calling, you need to complete Get token or the corresponding login-free authentication, and carry Authorization: Bearer <access_token> in the request header.
• If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail.
• Category: Authentication API.