{"data":{"id":"103219","string_id":"sL6a35","status":"1","parent_id":"0","slug":"rLWDgM","order":"6","name":"Product Guide","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"","published_time":"1719219300","add_time":"1717056048","update_time":"1778060124","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"child":[{"id":"783024","string_id":"7wBgueqn","status":"1","parent_id":"103219","slug":"7wBgueqn","order":"9","name":"Industrial Robots","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Zoe LEE","published_time":"0","add_time":"1778040237","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","pure_content":""},{"id":"783023","string_id":"uF7uDgtj","status":"1","parent_id":"103219","slug":"uF7uDgtj","order":"8","name":"Service Robots","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Zoe LEE","published_time":"0","add_time":"1778040209","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","pure_content":""},{"id":"782822","string_id":"7qW7xTi1","status":"1","parent_id":"103219","slug":"7qW7xTi1","order":"7","name":"Cleaning Robots","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Zoe LEE","published_time":"0","add_time":"1778033856","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","pure_content":""},{"id":"783553","string_id":"ziwUmO8V","status":"1","parent_id":"103219","slug":"ziwUmO8V","order":"6","name":"IoT","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Zoe LEE","published_time":"0","add_time":"1778059531","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","pure_content":""},{"id":"116782","string_id":"m8RM3w","status":"1","parent_id":"103219","slug":"dmymY0","order":"5","name":"Robot Accessories","type":"1","cover":"","cover_alt":"","desc":"","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"","published_time":"0","add_time":"1719456185","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","pure_content":""},{"id":"292288","string_id":"FknXLV8f","status":"1","parent_id":"103219","slug":"e-manual-download","order":"4","name":"E-Version User Manuals of PUDU Products","type":"1","cover":"","cover_alt":"","desc":"<\/colgroup>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Category<\/strong><\/td>\n

E-version user manual<\/strong><\/td>\n<\/tr>\n

Robots<\/td>\n

PUDU T300 User Manual-multilanguage-1220.pdf<\/a><\/td>\n<\/tr>\n

FlashBot User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

BellaBot Pro User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

BellaBot User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

KettyBot Pro User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

KettyBot User Manual_V1.0.pdf<\/a><\/td>\n<\/tr>\n

PUDU HolaBot User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU SwiftBot User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PuduBot 2 User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU_SH1 User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU CC1 User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU_CC1_Pro_User_Manual_multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU MT1 User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU_MT1_Vac_User_Manual_multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU_MT1_Max_User_Manual_multilanguage.pdf<\/a><\/td>\n<\/tr>\n

Accessories<\/td>\n

PUDU Charging Station Light User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU Mobile Water Station User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

CC1 Charging Station User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

CC1 Docking Station User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU_CC1_Seires_SelfCleaning_Docking_Station(Main)_User_Manual_multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU_CC1_Seires_SelfCleaning_Docking_Station(Base)_User_Manual_multilanguage.pdf<\/a><\/td>\n<\/tr>\n

MT1 Charging Station User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

Pudu GW1 User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

Pudu Pager User Manual-multilanguage.pdf<\/a><\/td>\n<\/tr>\n

PUDU 4G Watch-multilanguage.pdf<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>","website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"\u5434\u8d24\u71d5","published_time":"1737529558","add_time":"1737529541","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","file_type":"","auth_id":"[\"-1\"]","pure_content":"Category\nE-version user manual\n\n\nRobots\nPUDU T300 User Manual-multilanguage-1220.pdf\n\n\nFlashBot User Manual-multilanguage.pdf\n\n\nBellaBot Pro User Manual-multilanguage.pdf\n\n\nBellaBot User Manual-mul"},{"id":"172674","string_id":"O1bCcWSg","status":"1","parent_id":"103219","slug":"ji-qi-ren-shi-yong-zhu-yi-shi-xiang-ji-bao-yang-wei-hu","order":"3","name":"Product Usage and Maintenance: Important Precautions","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Product Usage and Maintenance: Important Precautions","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"\u9093\u4f73\u7389","published_time":"1727418679","add_time":"1727418365","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"3","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"172674","content":"

Download<\/strong>
To download the PDF version of this document, please click here: Product Usage and Maintenance: Important Precautions.pdf<\/a><\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n

From: PUDU after-sales service Dept.<\/strong><\/p>\n<\/td>\n<\/tr>\n

No.\uff1aPD-Tech-016<\/strong><\/p>\n<\/td>\n<\/tr>\n<\/thead>\n

Subject: Technical notice for precautions in usage and maintenance<\/strong><\/p>\n<\/td>\n<\/tr>\n

Content<\/strong><\/h2>\n
\n
\n
Precautions for daily use<\/p>\n<\/li>\n
\n
Power supply and usage instructions<\/p>\n<\/li>\n
\n
Maintenance<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n

1. Precautions for daily use<\/strong><\/h2>\n
Before use<\/strong><\/h3>\n
\n
\n
Before starting up, move the robot to the the starting point (laser positioning) or place it underneath \/ in front of the location code (marker positioning, fusion positioning).<\/p>\n<\/li>\n
\n
Blocking the radar, RGBD, top marker camera, or any similar sensors with any foreign object is strictly prohibited.<\/p>\n<\/li>\n
\n
Do not use the robot in the room temperature which is higher than 40 \u2103 or lower than 0 \u2103.<\/p>\n<\/li>\n
\n
Remove sharp objects, various wires, liquids, viscous objects and other foreign matters on the robot's running path.<\/p>\n<\/li>\n
\n
In some risky places, for example: stair\/escalator entrances, slopes with cliffs, and steps beside the path, please be sure to follow the prevention-falling set up solution, otherwise accidents may occur.<\/p>\n<\/li>\n<\/ol>\n
In use<\/strong><\/h3>\n
\n
\n
Do not block the robot suddenly during operation, otherwise safety accidents may occur.<\/p>\n<\/li>\n
\n
Do not adjust the items on the tray while the robot is moving, please click the screen to stop the robot and make adjustment.<\/p>\n<\/li>\n
\n
After the robot delivers food to the designated table, serve the food after the robot has stopped and stay steady.<\/p>\n<\/li>\n
\n
If the robot does not follow the set path or other emergencies occur, please press the red emergency stop button immediately.<\/p>\n<\/li>\n<\/ol>\n
Other precautions<\/strong><\/h3>\n
\n
\n
To ensure safety, it is recommended to adjust the running speed of the robot to 0.8m\/s or below, and the cruising speed to 0.5 m\/s–0.6 m\/s.<\/p>\n<\/li>\n
\n
It is not recommended to deliver high temperature liquid dishes, such as soup, hot pot, etc., which may cause liquid spilling or other accidents.<\/p>\n<\/li>\n
\n
If the robot has not been used for a long time, to prevent short circuit caused by humidity, ensure that the robot surface is dry and clean before starting up again. Additionally, carefully examine the assembly of robot accessories to avoid any damage resulting from improper assembly.<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n

2. Power supply and usage instructions<\/strong><\/h2>\n
Before charging<\/strong><\/h3>\n
\n
\n
Please assign specific personnel to charge the machine. It is recommended to start charging when someone is on duty.<\/p>\n<\/li>\n
\n
Protect the power cord of the charger carefully, do not to pull or twist it.<\/p>\n<\/li>\n
\n
Make sure that the power supply voltage meets the voltage requirements marked on the charger, otherwise the charger may be damaged.<\/p>\n<\/li>\n
\n
If the charger is damaged or work abnormally, please stop charging immediately and replace a new one in time.<\/p>\n<\/li>\n<\/ol>\n
Charging<\/strong><\/h3>\n
\n
\n
Do not use non-original charger to charge the robot.<\/p>\n<\/li>\n
\n
Do not charge the robot in the environment where it is near flammable and explosive objects.<\/p>\n<\/li>\n
\n
Make sure the environment where the robot is stored and charged dry and clean.<\/p>\n<\/li>\n
\n
If the robot sends an alarm when charging, please disconnect the power supply immediately.<\/p>\n<\/li>\n<\/ol>\n
Others<\/strong><\/h3>\n
\n
\n
After charging, please disconnect the power supply in time, and do not charge the machine for a long time when it is full.<\/p>\n<\/li>\n
\n
When the remaining power of the robot is less than 20%, please charge it in time. Prolonged low battery operation (less than 10%) may shorten battery life.<\/p>\n<\/li>\n
\n
When the power is lower than 2%, the battery will be in the protection state, the robot will not be able to perform tasks at this time, it should be charged before carrying on any task again.<\/p>\n<\/li>\n
\n
If the robot will not be used for a long time, please turn the key switch to OFF to protect the battery. If the charger will not be used for a long upcoming time, the power supply shall be completely disconnected.<\/p>\n<\/li>\n
\n
If the robot needs to be stored for a long time, it must be charged to more than 60% and the key switch must be turned to OFF. The battery shall be charged every 3 months to keep its activity.<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n

3. Maintenance<\/strong><\/h2>\n
Hardware maintenance<\/strong><\/h3>\n
\n
\n
Tray, screen, drive wheel and auxiliary wheel<\/strong> --- Check and clean the tray at least once a week, use a clean cloth to clean the screen. If the wheels are entangled by hair or stuck by debris, the robot must be placed transversely, or wheels been removed before cleaning.<\/p>\n<\/li>\n
\n
Sensor maintenance<\/strong> --- Clean the top marker camera, RGBD and radar at least once a week (use soft tissue or other lens cleaning supplies). In case of sudden dirt, be sure to clean it immediately to avoid the abnormal operation due to the shielding of the sensor.<\/p>\n<\/li>\n
\n
Maintenance of the machine body<\/strong> --- Wipe the machine body with a clean cotton cloth once a week to keep it clean. If the robot cannot work properly, do not disassemble it without permission or guidance from Pudu.<\/p>\n<\/li>\n
\n
Maintenance of cleaning components<\/strong> --- To obtain information on how to maintain the cleaning components, please access the Distributor Cloud Platform. Navigate to the Learning Center and enter Pudu Academy (academy.pudutech.com<\/a>). It is crucial to prioritize regular maintenance of the cleaning components and consumables for every robot model. This ensures cleanliness and extends the overall lifespan of the robot.<\/p>\n<\/li>\n<\/ol>\n
Storage and move<\/strong><\/h3>\n
\n
\n
Storage<\/strong> --- Make sure the storage environment clean and dry to prevent the intrusion from rats, cockroaches and other foreign matters.<\/p>\n<\/li>\n
\n
Move<\/strong> --- When it is necessary to move the robot, please follow the handling instructions provided in the product user manual. During the transportation process, it is crucial to maintain a balanced and upright posture of the robot.<\/p>\n<\/li>\n
\n
Marker maintenance<\/strong> --- Do not hung any other objects (such as balloons, barbed wire, slogans, etc.) under the markers on the ceiling, and markers shall not be damaged during ceiling cleaning and maintenance.<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
<\/p>","pure_content":"DownloadTo download the PDF version of this document, please click here: Product Usage and Maintenance: Important Precautions.pdf\n\n\n\n To: All Dealers\n Company:\nSHENZHEN PUDU TECHNOLOGY CO., LTD\n\n\n From: PUDU after-sales service Dept.\n\n\n Date\uff1a20\/9\/2024\n\n\n No.\uff1aPD-Tech-016\n\n\n\n\n Subject: Technical notice for precautions in usage and maintenance\n\n\n Content\n\n\nPrecautions for daily use\n\n\nPower supply and usage instructions\n\n\nMaintenance\n\n\n 1. Precautions for daily use\nBefore use\n\n\nBefore starting up, move the robot to the the starting point (laser positioning) or place it underneath \/ in front of the location code (marker positioning, fusion positioning).\n\n\nBlocking the radar, RGBD, top marker camera, or any similar sensors with any foreign object is strictly prohibited.\n\n\nDo not use the robot in the room temperature which is higher than 40 \u2103 or lower than 0 \u2103.\n\n\nRemove sharp objects, various wires, liquids, viscous objects and other foreign matters on the robot's running path.\n\n\nIn some risky places, for example: stair\/escalator entrances, slopes with cliffs, and steps beside the path, please be sure to follow the prevention-falling set up solution, otherwise accidents may occur.\n\n\nIn use\n\n\nDo not block the robot suddenly during operation, otherwise safety accidents may occur.\n\n\nDo not adjust the items on the tray while the robot is moving, please click the screen to stop the robot and make adjustment.\n\n\nAfter the robot delivers food to the designated table, serve the food after the robot has stopped and stay steady.\n\n\nIf the robot does not follow the set path or other emergencies occur, please press the red emergency stop button immediately.\n\n\nOther precautions\n\n\nTo ensure safety, it is recommended to adjust the running speed of the robot to 0.8m\/s or below, and the cruising speed to 0.5 m\/s\u20130.6 m\/s.\n\n\nIt is not recommended to deliver high temperature liquid dishes, such as soup, hot pot, etc., which may cause liquid spilling or other accidents.\n\n\nIf the robot has not been used for a long time, to prevent short circuit caused by humidity, ensure that the robot surface is dry and clean before starting up again. Additionally, carefully examine the assembly of robot accessories to avoid any damage resulting from improper assembly.\n\n\n 2. Power supply and usage instructions\nBefore charging\n\n\nPlease assign specific personnel to charge the machine. It is recommended to start charging when someone is on duty.\n\n\nProtect the power cord of the charger carefully, do not to pull or twist it.\n\n\nMake sure that the power supply voltage meets the voltage requirements marked on the charger, otherwise the charger may be damaged.\n\n\nIf the charger is damaged or work abnormally, please stop charging immediately and replace a new one in time.\n\n\nCharging\n\n\nDo not use non-original charger to charge the robot.\n\n\nDo not charge the robot in the environment where it is near flammable and explosive objects.\n\n\nMake sure the environment where the robot is stored and charged dry and clean.\n\n\nIf the robot sends an alarm when charging, please disconnect the power supply immediately.\n\n\nOthers\n\n\nAfter charging, please disconnect the power supply in time, and do not charge the machine for a long time when it is full.\n\n\nWhen the remaining power of the robot is less than 20%, please charge it in time. Prolonged low battery operation (less than 10%) may shorten battery life.\n\n\nWhen the power is lower than 2%, the battery will be in the protection state, the robot will not be able to perform tasks at this time, it should be charged before carrying on any task again.\n\n\nIf the robot will not be used for a long time, please turn the key switch to OFF to protect the battery. If the charger will not be used for a long upcoming time, the power supply shall be completely disconnected.\n\n\nIf the robot needs to be stored for a long time, it must be charged to more than 60% and the key switch must be turned to OFF. The battery shall be charged every 3 months to keep its activity.\n\n\n 3. Maintenance\nHardware maintenance\n\n\nTray, screen, drive wheel and auxiliary wheel --- Check and clean the tray at least once a week, use a clean cloth to clean the screen. If the wheels are entangled by hair or stuck by debris, the robot must be placed transversely, or wheels been removed before cleaning.\n\n\nSensor maintenance --- Clean the top marker camera, RGBD and radar at least once a week (use soft tissue or other lens cleaning supplies). In case of sudden dirt, be sure to clean it immediately to avoid the abnormal operation due to the shielding of the sensor.\n\n\nMaintenance of the machine body --- Wipe the machine body with a clean cotton cloth once a week to keep it clean. If the robot cannot work properly, do not disassemble it without permission or guidance from Pudu.\n\n\nMaintenance of cleaning components --- To obtain information on how to maintain the cleaning components, please access the Distributor Cloud Platform. Navigate to the Learning Center and enter Pudu Academy (academy.pudutech.com). It is crucial to prioritize regular maintenance of the cleaning components and consumables for every robot model. This ensures cleanliness and extends the overall lifespan of the robot.\n\n\nStorage and move\n\n\nStorage --- Make sure the storage environment clean and dry to prevent the intrusion from rats, cockroaches and other foreign matters.\n\n\nMove --- When it is necessary to move the robot, please follow the handling instructions provided in the product user manual. During the transportation process, it is crucial to maintain a balanced and upright posture of the robot.\n\n\nMarker maintenance --- Do not hung any other objects (such as balloons, barbed wire, slogans, etc.) under the markers on the ceiling, and markers shall not be damaged during ceiling cleaning and maintenance.\n\n\n\n\u00a0","is_draft":"0","editor_type":"3","file_path":"","add_time":"1727418365","update_time":"1734942666"},"pure_content":"DownloadTo download the PDF version of this document, please click here: Product Usage and Maintenance: Important Precautions.pdf\n\n\n\n To: All Dealers\n Company:\nSHENZHEN PUDU TECHNOLOGY CO., LTD\n\n\n Fro"},{"id":"268385","string_id":"eJLlN0ik","status":"1","parent_id":"103219","slug":"mian-deng-lu-zhi-yin","order":"2","name":"Guide for Accessing Without Login","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Guide for Accessing Without Login","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"\u9093\u4f73\u7389","published_time":"1735809021","add_time":"1735808721","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"3","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"268385","content":"
Login-free<\/strong> Configuration Guide<\/h2>\n
\u26a0\ufe0f ATTENTION !<\/strong><\/p>\n
\n
Make sure your authorization service can be accessed normally, otherwise the request may fail<\/li>\n
Make sure your relevant request address and URL information are filled in correctly, otherwise the request will not be able to proceed normally<\/li>\n
Considering the differences in authorization server requests and return data of different companies, you need to fill in the request template when configuring. The template supports five placeholders: {ClientId}, {ClientSecret}, {Code}, {AccessToken}, {AccessTokenType}. You need to fill in the correct placeholders in the template. Only one level of nesting is supported, not multiple levels of nesting.<\/li>\n
The Content-Type of the HTTP request is application\/json. When obtaining user information, the HTTP Header will automatically carrythe Authorization: {AccessToken} or Authorization: Bearer {AccessToken} key- value pair.<\/li>\n<\/ol>\n
1. Business Request Process<\/h2>\n
$\"descript\"$ <\/p>\n
2. Placeholder Description<\/h2>\n\n\n\n\n\n\n\n\n\n\n
Placeholder<\/strong><\/td>\n meaning<\/strong><\/td>\n<\/tr>\n
{ClientId}<\/strong><\/td>\n \n
Your company's authorization server generates the ClientId<\/strong><\/p>\n
In [Login-free Configuration], the placeholder format used in your request parameters, return parameters, and URL must be:{ClientId}<\/strong><\/p>\n<\/td>\n<\/tr>\n
{ClientSecret}<\/strong><\/td>\n \n
Your company's authorization server generates a ClientSecret<\/strong><\/p>\n
In [Login-free Configuration], the placeholder format used in your request parameters, return parameters, and URLs must be:{ClientSecret}<\/strong><\/p>\n<\/td>\n<\/tr>\n
{Code}<\/strong><\/td>\n \n
The code that your company's authorization server calls back after the user authorizes<\/strong><\/p>\n
In [Login-free Configuration], the format of the placeholders used in your request parameters, return parameters, and URLs must be:{Code}<\/strong><\/p>\n<\/td>\n<\/tr>\n
{AccessToken}<\/strong><\/td>\n \n
The token obtained by calling the configured [<\/strong> Get Token URL ] through the [code] callback of the authorization server can be used to obtain user information<\/p>\n
In [Login-free Configuration], the placeholder format used in your request parameters, return parameters, and URL must be:{AccessToken}<\/strong><\/p>\n<\/td>\n<\/tr>\n
{AccessTokenType}<\/strong><\/td>\n \n
The token type obtained by calling the [<\/strong> Get Token URL ] configured by the [code] callback of the authorization server . Currently, only thebearer<\/strong> type is supported.<\/p>\n
In [Login-free Configuration], the format of the placeholders used in your request parameters, return parameters, and URLs must be:{AccessTokenType}<\/strong><\/p>\n<\/td>\n<\/tr>\n
{MatchPuDuAccount}<\/strong><\/td>\n \n
The user information is obtained through the token issued by your authorization service. The field where the user information you return matches the Purdue account. The placeholder must be:<\/strong><\/p>\n
{MatchPuDuAccount}<\/strong><\/p>\n<\/td>\n<\/tr>\n
{RedirectUri}<\/strong><\/td>\n \n
If your authorization server has validation for RedirectUri, please use it in your API request parameters for obtaining tokens or obtaining users. The placeholder must be:<\/strong><\/p>\n
{RedirectUri}<\/strong><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
3. \"Login-free configuration\" Parameter description<\/strong><\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n
parameter<\/strong><\/td>\n Request method<\/strong><\/td>\n URL parameter template description<\/strong><\/td>\n Request parameter template description<\/strong><\/td>\n Return parameter template description<\/strong><\/td>\n Parameter Description<\/strong><\/td>\n<\/tr>\n
Client ID<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Generated by the enterprise<\/strong><\/td>\n<\/tr>\n
Client Secret<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Generated by the enterprise<\/strong><\/td>\n<\/tr>\n
Authorization server URL<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n This address can be used to learn about the relevant documents of the company's own OAuth2 service<\/strong><\/td>\n<\/tr>\n
Get the Token URL<\/strong><\/td>\n GET<\/strong><\/td>\n \n
Call this interface via GET when sending an HTTP request<\/strong><\/p>\n
that<\/strong>the original request ishttps:\/\/xxxxx.com\/oauth\/token?client_id=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc&client_secret =d34cce4ca0b9116340451c2000a9af216d5b209579c7567b63347b38d6100b81&code= a0b9116340<\/p>\n
Then the placeholder is:<\/strong><\/p>\n
https:\/\/xxxxx.com\/oauth\/token?client_id<\/strong>= {ClientId}<\/strong> & client_secret = { ClientSecret}<\/strong> & code={Code}<\/p>\n<\/td>\n
Not involved<\/strong><\/td>\n \n
If your interface returns the following parameter:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"access_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",<\/strong><\/p>\n
\"refresh_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",<\/strong><\/p>\n
\"token_type\": \"bearer\"<\/strong><\/p>\n
}<\/strong><\/p>\n
The template to be filled in is:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"access_token\": \"{AccessToken}<\/strong> \",<\/p>\n
\"refresh_token\": \"{refreshTokenType}<\/strong> \",<\/p>\n
\"token_type\": \"{AccessTokenType}<\/strong> \"<\/p>\n
}<\/strong><\/p>\n<\/td>\n
\n
1.<\/strong> The interface only supports two HTTP request methods: GET and POST<\/p>\n
2.<\/strong> If there are other fixed ones written directly in it, the request will expire when requested.<\/p>\n
3.<\/strong> POST parameters support BODY RAW request method<\/p>\n
4.<\/strong> The request header automatically carries:Content-Type: application\/json<\/p>\n
5.<\/strong> Make sure that the returned parameters can obtain user information through the token, otherwise you will not be able to log in normally<\/p>\n
<\/p>\n<\/td>\n<\/tr>\n
POST<\/strong><\/td>\n \n
Call this interface via POST when sending an HTTP request<\/strong><\/p>\n
Assume that the original request interface is:<\/strong> https:\/\/xxxxx.com\/oauth\/token?client_id=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc&client_secret=d34cce4ca0b9116340451c2000a9af216d5b209579c7567b63347b38d6100b81&code= a0b9116340<\/p>\n
Then the placeholder is:<\/strong><\/p>\n
https:\/\/xxxxx.com\/oauth\/token?client_id<\/a>={ClientId}<\/strong> & client_secret = { ClientSecret}<\/strong> & code= {Code}<\/strong><\/p>\n<\/td>\n
\n
If your interface request parameters are:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"client_id<\/strong> \": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",<\/p>\n
\"client_secret<\/strong> \": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\"<\/p>\n
}<\/strong><\/p>\n
The template to be filled in is:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"<\/strong>client_id \": \" { ClientId }<\/strong> \",<\/p>\n
\"<\/strong>client_secret \": \" { ClientSecret }<\/strong> \"<\/p>\n
}<\/strong><\/p>\n<\/td>\n
\n
If your interface returns the following parameter:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"access_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",<\/strong><\/p>\n
\"refresh_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",<\/strong><\/p>\n
\"token_type\": \"bearer\"<\/strong><\/p>\n
}<\/strong><\/p>\n
The template to be filled in is:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"access_token\": \"{AccessToken}<\/strong> \",<\/p>\n
\"refresh_token\": \"{refreshTokenType}<\/strong> \",<\/p>\n
\"token_type\": \"{AccessTokenType}<\/strong> \"<\/p>\n
}<\/strong><\/p>\n<\/td>\n<\/tr>\n
Get user information URL<\/strong><\/td>\n GET<\/strong><\/td>\n \n
Call this interface via GET when sending an HTTP request<\/strong><\/p>\n
Assume that the original request interface<\/strong> is : https:\/\/xxxxx.com\/api\/v5\/user?access_token=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc<\/p>\n
Then the placeholder is:<\/strong><\/p>\n
https:\/\/xxxxx.com\/api\/v5\/user?access_token<\/a>= {AccessToken}<\/strong><\/p>\n<\/td>\n
\n
Not involved<\/strong><\/p>\n
<\/p>\n<\/td>\n
\n
If your interface returns the following parameter:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"user_id\":\"xxxxxxxxx\",<\/strong><\/p>\n
\"email\":\"xxxx@xx.com\",<\/strong><\/p>\n
\"name\": \"xxxxxxxxx\"<\/strong><\/p>\n
}<\/strong><\/p>\n
The template to be filled in is:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"user_id\":\"xxxxxxxxx\",<\/strong><\/p>\n
\"email\":\"{MatchPuDuAccount}\",<\/strong><\/p>\n
\"name\": \"xxxxxxxxx\"<\/strong><\/p>\n
}<\/strong><\/p>\n<\/td>\n
\n
1.<\/strong> The interface only supports two HTTP request methods: GET and POST<\/p>\n
2.<\/strong> If there are other fixed ones written directly in it, the request will expire when requested.<\/p>\n
3.<\/strong> POST parameters support BODY RAW request method<\/p>\n
4.<\/strong> The request header automatically carries:Content-Type: application\/json<\/p>\n
5.<\/strong> Please make sure that the matching fields in the returned parameters match the Purdue login account, otherwise the login will fail.<\/p>\n
6.<\/strong> When calling the user information interface, the HTTP Header will automatically include the Authorization: {AccessToken} or Authorization:Bearer {AccessToken} key-value pair<\/p>\n<\/td>\n<\/tr>\n
POST<\/strong><\/td>\n \n
Call this interface via GET when sending an HTTP request<\/strong><\/p>\n
Assume that the original request interface<\/strong> is : https:\/\/xxxxx.com\/api\/v5\/user?access_token=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc<\/p>\n
Then the placeholder is:<\/strong><\/p>\n
https:\/\/xxxxx.com\/api\/v5\/user?access_token<\/a>= {AccessToken}<\/strong><\/p>\n<\/td>\n
\n
If your interface request parameters are:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"<\/strong>access_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\"<\/p>\n
}<\/strong><\/p>\n
The template to be filled in is:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"<\/strong>access_token\": \"{AccessToken}<\/strong> \"<\/p>\n
}<\/strong><\/p>\n<\/td>\n
\n
If your interface returns the following parameter:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"user_id\":\"xxxxxxxxx\",<\/strong><\/p>\n
\"email\":\"xxxx@xx.com\",<\/strong><\/p>\n
\"name\": \"xxxxxxxxx\"<\/strong><\/p>\n
}<\/strong><\/p>\n
The template to be filled in is:<\/strong><\/p>\n
{<\/strong><\/p>\n
\"user_id\":\"xxxxxxxxx\",<\/strong><\/p>\n
\"email\":\"{MatchPuDuAccount}\",<\/strong><\/p>\n
\"name\": \"xxxxxxxxx\"<\/strong><\/p>\n
}<\/strong><\/p>\n<\/td>\n<\/tr>\n
Account Matching Field<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n <\/td>\n The user information obtained by calling the [<\/strong> Get User Information URL ] interface matches the Purdue login account field<\/td>\n<\/tr>\n
Redirect address<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n Not involved<\/strong><\/td>\n <\/td>\n The redirection address jumps to the enterprise's authorization server to achieve the login-free function. After filling in the above configuration information, it is automatically generated.<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
4. Configuration process description (taking GITHUB as an example)<\/h2>\n
\n
The first step is to register a github third-party application.
Homepage URL:<\/strong> fill in as you like
Callback URL:<\/strong> [Purdue Certification Service Address]\/v1\/redirect
$\"descript\"$ <\/li>\n
the second step is to generate a Client in the created github application. secrets
be sure to keep your Client secrets, don't divulge.
$\"descript\"$
After obtaining the Client ID and Client secret, go to the next step<\/li>\n
step 3: Find the corresponding Purdue business platform for configuration
This is an example of the Purdue agent platform.
$\"descript\"$
The Client ID & Client Secret has been obtained through the application of github. Next, follow Authenticating to the REST API with an OAuth app <\/a>to make the relevant configuration.<\/li>\n<\/ol>\n
\n
Authorization Server URL:<\/li>\n<\/ul>\n
that is, the authorization address of the Github authorization server. https:\/\/github.com\/login\/oauth\/authorize<\/a><\/p>\n
if your application needs to bring more parameters, you can configure them here.<\/p>\n
\n
Get the Token:<\/li>\n<\/ul>\n
the interface of access_token is obtained by using the code (authorization code) called back by the authorization server.<\/p>\n
By configuring the request parameters and returning data, through placeholders (refer to the above \u3010 placeholder Description<\/strong> ])<\/p>\n
$\"descript\"$ <\/p>\n
\n
Get user information:<\/li>\n<\/ul>\n
you can use the access_token and token_type obtained through the preceding API to obtain user information. After obtaining the user information, it will return the data you configured through {MatchPuDuAccount}<\/strong> placeholder to match the account number field in the Purdue account number.<\/p>\n
\n
\n
\n
Note that currently only the token_type of the bearers is supported. If it is not passed, it will be passed in the header by default. Pass the Authorization value.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
$\"descript\"$ <\/p>\n
After the configuration is completed and saved successfully. A jump address will be generated below.<\/p>\n
Shaped: [Purdue Certification Service Address]\/v1\/jump\/\u3010 Client ID ]]<\/p>\n
HTTPS:\/\/LOGIN-CXG-TEST-INTEMALPUDU.WORK\/V1JUMP\/LV23LITOU6E04YUBRZVG<\/p>\n
jump Address<\/p>\n
$\"descript\"$ <\/p>\n
if you need to jump to a specified address, you can specify the jump by adding the redirect_uri parameter to the jump address (note that this parameter needs to be encoded).<\/p>\n
5. Common errors<\/h2>\n
If an error message appears during use and the prefix of the message is the error code, the possible error causes are as follows:<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n
Error Code<\/strong><\/td>\n Possible Causes of Errors<\/strong><\/td>\n<\/tr>\n
\n
3133<\/strong><\/p>\n<\/td>\n
\n
the user matching field is filled in. The interface for obtaining user information on your authorization server does not return the modified field or the returned field is null.<\/p>\n<\/td>\n<\/tr>\n
\n
3134<\/strong><\/p>\n<\/td>\n
\n
please check whether your authorization server has returned authorization code normally<\/p>\n<\/td>\n<\/tr>\n
\n
3135<\/strong><\/p>\n<\/td>\n
\n
error in obtaining your authorization configuration information, please check whether your login-free configuration is correct.<\/p>\n<\/td>\n<\/tr>\n
\n
3137<\/strong><\/p>\n<\/td>\n
\n
the token url for obtaining your Authorization Service or the url for obtaining user information is incorrect, please check whether your login-free configuration is correct.<\/p>\n<\/td>\n<\/tr>\n
\n
3138<\/strong><\/p>\n<\/td>\n
\n
parsing your get token url error, please check whether your get token url placeholder is used correctly.<\/p>\n<\/td>\n<\/tr>\n
\n
3139<\/strong><\/p>\n<\/td>\n
\n
an error occurred in calling your url to obtain the token. Please check whether your url is correctly filled in, your url request parameters are correct, and your url request parameter placeholder is used correctly. If your authorization server has mandatory verification of [redirect_uri], please check whether your callback address in your authorization server is correctly filled in<\/p>\n<\/td>\n<\/tr>\n
\n
3140<\/strong><\/p>\n<\/td>\n
\n
when calling your url to obtain the token, an error occurred when parsing the return parameter. Please check whether the placeholder for your return parameter is correct.<\/p>\n<\/td>\n<\/tr>\n
\n
3141<\/strong><\/p>\n<\/td>\n
\n
An error occurred in calling your url for obtaining user information. Check whether your url is correctly filled in and whether your url request parameters are correct.<\/p>\n<\/td>\n<\/tr>\n
\n
3142<\/strong><\/p>\n<\/td>\n
\n
you authorize the user information returned by the server. After the matching fields are obtained, the account status of the Purdue system is abnormal. Please log in to the Purdue system to modify the current account status.<\/p>\n<\/td>\n<\/tr>\n
\n
3144<\/strong><\/p>\n<\/td>\n
\n
the user information you returned did not match the Purdue system account after obtaining the matching field.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>","pure_content":"Login-free Configuration Guide\n\u26a0\ufe0f ATTENTION !\n\nMake sure your authorization service can be accessed normally, otherwise the request may fail\nMake sure your relevant request address and URL information are filled in correctly, otherwise the request will not be able to proceed normally\nConsidering the differences in authorization server requests and return data of different companies, you need to fill in the request template when configuring. The template supports five placeholders: {ClientId}, {ClientSecret}, {Code}, {AccessToken}, {AccessTokenType}. You need to fill in the correct placeholders in the template. Only one level of nesting is supported, not multiple levels of nesting.\nThe Content-Type of the HTTP request is application\/json. When obtaining user information, the HTTP Header will automatically carrythe Authorization: {AccessToken} or Authorization: Bearer {AccessToken} key- value pair.\n\n1. Business Request Process\n\n2. Placeholder Description\n\n\n\n Placeholder\n meaning\n\n\n {ClientId}\n Your company's authorization server generates the ClientId\nIn [Login-free Configuration], the placeholder format used in your request parameters, return parameters, and URL must be:{ClientId}\n\n\n {ClientSecret}\n Your company's authorization server generates a ClientSecret\nIn [Login-free Configuration], the placeholder format used in your request parameters, return parameters, and URLs must be:{ClientSecret}\n\n\n {Code}\n The code that your company's authorization server calls back after the user authorizes\nIn [Login-free Configuration], the format of the placeholders used in your request parameters, return parameters, and URLs must be:{Code}\n\n\n {AccessToken}\n The token obtained by calling the configured [ Get Token URL ] through the [code] callback of the authorization server can be used to obtain user information\nIn [Login-free Configuration], the placeholder format used in your request parameters, return parameters, and URL must be:{AccessToken}\n\n\n {AccessTokenType}\n The token type obtained by calling the [ Get Token URL ] configured by the [code] callback of the authorization server . Currently, only thebearer type is supported.\nIn [Login-free Configuration], the format of the placeholders used in your request parameters, return parameters, and URLs must be:{AccessTokenType}\n\n\n {MatchPuDuAccount}\n The user information is obtained through the token issued by your authorization service. The field where the user information you return matches the Purdue account. The placeholder must be:\n{MatchPuDuAccount}\n\n\n {RedirectUri}\n If your authorization server has validation for RedirectUri, please use it in your API request parameters for obtaining tokens or obtaining users. The placeholder must be:\n{RedirectUri}\n\n\n\n3. \"Login-free configuration\" Parameter description\n\n\n\n parameter\n Request method\n URL parameter template description\n Request parameter template description\n Return parameter template description\n Parameter Description\n\n\n Client ID\n Not involved\n Not involved\n Not involved\n Not involved\n Generated by the enterprise\n\n\n Client Secret\n Not involved\n Not involved\n Not involved\n Not involved\n Generated by the enterprise\n\n\n Authorization server URL\n Not involved\n Not involved\n Not involved\n Not involved\n This address can be used to learn about the relevant documents of the company's own OAuth2 service\n\n\n Get the Token URL\n GET\n Call this interface via GET when sending an HTTP request\nthatthe original request ishttps:\/\/xxxxx.com\/oauth\/token?client_id=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc&client_secret =d34cce4ca0b9116340451c2000a9af216d5b209579c7567b63347b38d6100b81&code= a0b9116340\nThen the placeholder is:\nhttps:\/\/xxxxx.com\/oauth\/token?client_id= {ClientId} & client_secret = { ClientSecret} & code={Code}\n Not involved\n If your interface returns the following parameter:\n{\n\"access_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",\n\"refresh_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",\n\"token_type\": \"bearer\"\n}\nThe template to be filled in is:\n{\n\"access_token\": \"{AccessToken} \",\n\"refresh_token\": \"{refreshTokenType} \",\n\"token_type\": \"{AccessTokenType} \"\n}\n 1. The interface only supports two HTTP request methods: GET and POST\n2. If there are other fixed ones written directly in it, the request will expire when requested.\n3. POST parameters support BODY RAW request method\n4. The request header automatically carries:Content-Type: application\/json\n5. Make sure that the returned parameters can obtain user information through the token, otherwise you will not be able to log in normally\n\u00a0\n\n\n POST\n Call this interface via POST when sending an HTTP request\nAssume that the original request interface is: https:\/\/xxxxx.com\/oauth\/token?client_id=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc&client_secret=d34cce4ca0b9116340451c2000a9af216d5b209579c7567b63347b38d6100b81&code= a0b9116340\nThen the placeholder is:\nhttps:\/\/xxxxx.com\/oauth\/token?client_id={ClientId} & client_secret = { ClientSecret} & code= {Code}\n If your interface request parameters are:\n{\n\"client_id \": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",\n\"client_secret \": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\"\n}\nThe template to be filled in is:\n{\n\"client_id \": \" { ClientId } \",\n\"client_secret \": \" { ClientSecret } \"\n}\n If your interface returns the following parameter:\n{\n\"access_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",\n\"refresh_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\",\n\"token_type\": \"bearer\"\n}\nThe template to be filled in is:\n{\n\"access_token\": \"{AccessToken} \",\n\"refresh_token\": \"{refreshTokenType} \",\n\"token_type\": \"{AccessTokenType} \"\n}\n\n\n Get user information URL\n GET\n Call this interface via GET when sending an HTTP request\nAssume that the original request interface is : https:\/\/xxxxx.com\/api\/v5\/user?access_token=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\nThen the placeholder is:\nhttps:\/\/xxxxx.com\/api\/v5\/user?access_token= {AccessToken}\n Not involved\n\u00a0\n If your interface returns the following parameter:\n{\n\"user_id\":\"xxxxxxxxx\",\n\"email\":\"xxxx@xx.com\",\n\"name\": \"xxxxxxxxx\"\n}\nThe template to be filled in is:\n{\n\"user_id\":\"xxxxxxxxx\",\n\"email\":\"{MatchPuDuAccount}\",\n\"name\": \"xxxxxxxxx\"\n}\n 1. The interface only supports two HTTP request methods: GET and POST\n2. If there are other fixed ones written directly in it, the request will expire when requested.\n3. POST parameters support BODY RAW request method\n4. The request header automatically carries:Content-Type: application\/json\n5. Please make sure that the matching fields in the returned parameters match the Purdue login account, otherwise the login will fail.\n6. When calling the user information interface, the HTTP Header will automatically include the Authorization: {AccessToken} or Authorization:Bearer {AccessToken} key-value pair\n\n\n POST\n Call this interface via GET when sending an HTTP request\nAssume that the original request interface is : https:\/\/xxxxx.com\/api\/v5\/user?access_token=bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\nThen the placeholder is:\nhttps:\/\/xxxxx.com\/api\/v5\/user?access_token= {AccessToken}\n If your interface request parameters are:\n{\n\"access_token\": \"bfe175c3180480253a228827c1c8a9393906d3808ccaea778e3dc70ebd2057fc\"\n}\nThe template to be filled in is:\n{\n\"access_token\": \"{AccessToken} \"\n}\n If your interface returns the following parameter:\n{\n\"user_id\":\"xxxxxxxxx\",\n\"email\":\"xxxx@xx.com\",\n\"name\": \"xxxxxxxxx\"\n}\nThe template to be filled in is:\n{\n\"user_id\":\"xxxxxxxxx\",\n\"email\":\"{MatchPuDuAccount}\",\n\"name\": \"xxxxxxxxx\"\n}\n\n\n Account Matching Field\n Not involved\n Not involved\n Not involved\n \u00a0\n The user information obtained by calling the [ Get User Information URL ] interface matches the Purdue login account field\n\n\n Redirect address\n Not involved\n Not involved\n Not involved\n \u00a0\n The redirection address jumps to the enterprise's authorization server to achieve the login-free function. After filling in the above configuration information, it is automatically generated.\n\n\n\n4. Configuration process description (taking GITHUB as an example)\n\nThe first step is to register a github third-party application.Homepage URL: fill in as you likeCallback URL: [Purdue Certification Service Address]\/v1\/redirect\nthe second step is to generate a Client in the created github application. secretsbe sure to keep your Client secrets, don't divulge.After obtaining the Client ID and Client secret, go to the next step\nstep 3: Find the corresponding Purdue business platform for configurationThis is an example of the Purdue agent platform.The Client ID & Client Secret has been obtained through the application of github. Next, follow\u00a0Authenticating to the REST API with an OAuth app to make the relevant configuration.\n\n\nAuthorization Server URL:\n\nthat is, the authorization address of the Github authorization server. https:\/\/github.com\/login\/oauth\/authorize\nif your application needs to bring more parameters, you can configure them here.\n\nGet the Token:\n\nthe interface of access_token is obtained by using the code (authorization code) called back by the authorization server.\nBy configuring the request parameters and returning data, through placeholders (refer to the above \u3010 placeholder Description ])\n\n\nGet user information:\n\nyou can use the access_token and token_type obtained through the preceding API to obtain user information. After obtaining the user information, it will return the data you configured through {MatchPuDuAccount} placeholder to match the account number field in the Purdue account number.\n\n\n\nNote that currently only the token_type of the bearers is supported. If it is not passed, it will be passed in the header by default. Pass the Authorization value.\n\n\n\n\nAfter the configuration is completed and saved successfully. A jump address will be generated below.\nShaped: [Purdue Certification Service Address]\/v1\/jump\/\u3010 Client ID ]]\nHTTPS:\/\/LOGIN-CXG-TEST-INTEMALPUDU.WORK\/V1JUMP\/LV23LITOU6E04YUBRZVG\njump Address\n\nif you need to jump to a specified address, you can specify the jump by adding the redirect_uri parameter to the jump address (note that this parameter needs to be encoded).\n5. Common errors\nIf an error message appears during use and the prefix of the message is the error code, the possible error causes are as follows:\n\n\n\n Error Code\n Possible Causes of Errors\n\n\n 3133\n the user matching field is filled in. The interface for obtaining user information on your authorization server does not return the modified field or the returned field is null.\n\n\n 3134\n please check whether your authorization server has returned authorization code normally\n\n\n 3135\n error in obtaining your authorization configuration information, please check whether your login-free configuration is correct.\n\n\n 3137\n the token url for obtaining your Authorization Service or the url for obtaining user information is incorrect, please check whether your login-free configuration is correct.\n\n\n 3138\n parsing your get token url error, please check whether your get token url placeholder is used correctly.\n\n\n 3139\n an error occurred in calling your url to obtain the token. Please check whether your url is correctly filled in, your url request parameters are correct, and your url request parameter placeholder is used correctly. If your authorization server has mandatory verification of [redirect_uri], please check whether your callback address in your authorization server is correctly filled in\n\n\n 3140\n when calling your url to obtain the token, an error occurred when parsing the return parameter. Please check whether the placeholder for your return parameter is correct.\n\n\n 3141\n An error occurred in calling your url for obtaining user information. Check whether your url is correctly filled in and whether your url request parameters are correct.\n\n\n 3142\n you authorize the user information returned by the server. After the matching fields are obtained, the account status of the Purdue system is abnormal. Please log in to the Purdue system to modify the current account status.\n\n\n 3144\n the user information you returned did not match the Purdue system account after obtaining the matching field.","is_draft":"0","editor_type":"3","file_path":"","add_time":"1735808721","update_time":"1735815598"},"pure_content":"Login-free Configuration Guide\n\u26a0\ufe0f ATTENTION !\n\nMake sure your authorization service can be accessed normally, otherwise the request may fail\nMake sure your relevant request address and URL information"},{"id":"325140","string_id":"lFKZUtGO","status":"1","parent_id":"103219","slug":"ti-jiao-zi-liao-xu-qiu-yu-fan-kui","order":"1","name":"Submit Information Needs and Feedback","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"Submit Information Needs and Feedback","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"\u9093\u4f73\u7389","published_time":"1739869434","add_time":"1739869233","update_time":"1778059866","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"3","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"325140","content":"
Welcome to the “Submit Information Needs and Feedback” page! We appreciate your input and aim to improve our services continually. Here’s how you can submit your needs and feedback.<\/p>\n
Submission Steps<\/h2>\n
1. Click the Link:<\/h3>\n
Click the \"Give feedback about this article\" button at the bottom of this article.<\/p>\n
$\"descript\"$ <\/p>\n
2. Fill Out the Form:<\/h3>\n
Please provide the following information:<\/p>\n
\n
Name: Your name (we’ll reward those who give great feedback)<\/li>\n
Email: Your contact information<\/li>\n
Submission Type: Information Request \/ Feedback \/ Self-made Documents Contribution<\/li>\n
Description: Clearly state your needs or comments<\/li>\n<\/ul>\n
$\"descript\"$ <\/p>\n
3. Submit the Form:<\/h3>\n
After completing the form, click the \"Submit\" button. Your feedback will be sent to us.<\/p>\n
How We Can Help<\/h2>\n
\n
Information Requests: Let us know if you need specific materials, and we’ll do our best to assist.<\/li>\n
Service Feedback: Your feedback is valuable for our improvement; any suggestions or compliments are welcome.<\/li>\n
Follow-Up: If we need more information, we may reach out to you.<\/li>\n<\/ul>\n
Your Voice Matters<\/h2>\n
Your feedback is important to us and helps us enhance our service quality. Thank you for taking the time to share your thoughts. We look forward to your feedback!<\/p>","pure_content":"Welcome to the \u201cSubmit Information Needs and Feedback\u201d page! We appreciate your input and aim to improve our services continually. Here\u2019s how you can submit your needs and feedback.\nSubmission Steps\n1. Click the Link:\nClick the \"Give feedback about this article\" button at the bottom of this article.\n\n2. Fill Out the Form:\nPlease provide the following information:\n\nName: Your name (we\u2019ll reward those who give great feedback)\nEmail: Your contact information\nSubmission Type: Information Request \/ Feedback \/ Self-made Documents Contribution\nDescription: Clearly state your needs or comments\n\n\n3. Submit the Form:\nAfter completing the form, click the \"Submit\" button. Your feedback will be sent to us.\nHow We Can Help\n\nInformation Requests: Let us know if you need specific materials, and we\u2019ll do our best to assist.\nService Feedback: Your feedback is valuable for our improvement; any suggestions or compliments are welcome.\nFollow-Up: If we need more information, we may reach out to you.\n\nYour Voice Matters\nYour feedback is important to us and helps us enhance our service quality. Thank you for taking the time to share your thoughts. We look forward to your feedback!","is_draft":"0","editor_type":"3","file_path":"","add_time":"1739869233","update_time":"1739876553"},"pure_content":"Welcome to the \u201cSubmit Information Needs and Feedback\u201d page! We appreciate your input and aim to improve our services continually. Here\u2019s how you can submit your needs and feedback.\nSubmission Steps\n1"}],"content":{"icon":"\/docker_production\/r7bv6l\/content_icon\/sL6a35?rand=2021901799","desc":"","content_id":"103219","add_time":"1717056048","update_time":"1745835304","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}

Content<\/strong><\/h2>\n\n\nPrecautions for daily use<\/p>\n<\/li>\n\nPower supply and usage instructions<\/p>\n<\/li>\n\nMaintenance<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n

1. Business Request Process<\/h2>\n<\/p>\n

Submission Steps<\/h2>\n

1. Click the Link:<\/h3>\nClick the \"Give feedback about this article\" button at the bottom of this article.<\/p>\n<\/p>\n

3. Submit the Form:<\/h3>\nAfter completing the form, click the \"Submit\" button. Your feedback will be sent to us.<\/p>\n

Content<\/strong><\/h2>\n
\n
\n
Precautions for daily use<\/p>\n<\/li>\n
\n
Power supply and usage instructions<\/p>\n<\/li>\n
\n
Maintenance<\/p>\n<\/li>\n<\/ol>\n<\/td>\n<\/tr>\n

1. Business Request Process<\/h2>\n
$\"descript\"$ <\/p>\n

1. Click the Link:<\/h3>\n
Click the \"Give feedback about this article\" button at the bottom of this article.<\/p>\n
$\"descript\"$ <\/p>\n

3. Submit the Form:<\/h3>\n
After completing the form, click the \"Submit\" button. Your feedback will be sent to us.<\/p>\n