2
0
Deben Oldert 10 жил өмнө
parent
commit
d494451fb7
1 өөрчлөгдсөн 21 нэмэгдсэн , 20 устгасан
  1. 21 20
      README.md

+ 21 - 20
README.md

@@ -19,30 +19,31 @@ Each part has its own folder in this repo. (Except for SAS and APS, same servlet
 There are 2 scenarios, 1 where the user has no device registered and 2 the case where there *is* a device registered.
 There are 2 scenarios, 1 where the user has no device registered and 2 the case where there *is* a device registered.
 ### Scenario 1
 ### Scenario 1
 A simple overview if the device is not registered in our APS:
 A simple overview if the device is not registered in our APS:
-> ARS send access request over RADIUS to NPS\
-> NPS extension receive access request\
-> NPS extension send authentication request to SAS\
-> SAS Authenticates the user via APS, APS returns NO userinfo\
-> SAS reply with code 2 (User needs device registration) and send sendmail request to APS\
-> APS sends email to user\
-> User follows instructions mail (Download from link and open from link)\
-> User logs in with device\
-> Device sends register request to SAS\
-> SAS forwards device registration request to APS\
-> APS registers device\
-> SAS sends result code to device
+1. ARS send access request over RADIUS to NPS
+2. NPS extension receive access request
+3. NPS extension send authentication request to SAS
+4. SAS Authenticates the user via APS, APS returns NO userinfo
+5. SAS reply with code 2 (User needs device registration) and send sendmail request to APS
+6. APS sends email to user
+7. User follows instructions mail (Download from link and open from link)
+8. User logs in with device
+9. Device sends register request to SAS
+10. SAS forwards device registration request to APS
+11. APS registers device
+12. SAS sends result code to device
 When this is done the user retry to login and will automaticly follow scenario 2
 When this is done the user retry to login and will automaticly follow scenario 2
 
 
 
 
 ### Scenarion 2
 ### Scenarion 2
 When a device is already registered in our APS it goes as followed:
 When a device is already registered in our APS it goes as followed:
-> ARS send access request over RADIUS to NPS
-> NPS extension receive access request
-> NPS extension send authentication request to SAS
-> SAS Authenticates the user via APS, APS return userInfo
-> SAS sends a PUSH notification to device
-> Device access response (approved or cancelled) is send to SAS
-> SAS replies to ARS with corresponding code
-> ARS proccesses the request (code 0= accept/ code 1=reject)
+1. ARS send access request over RADIUS to NPS
+2. NPS extension receive access request
+3. NPS extension send authentication request to SAS
+4. SAS Authenticates the user via APS, APS return userInfo
+5. SAS sends a PUSH notification to device
+6. Device access response (approved or cancelled) is send to SAS
+7. SAS replies to ARS with corresponding code
+8. ARS proccesses the request (code 0= accept/ code 1=reject)
+9. YEAAAH, user just logged in!!! (If we have chosen grand access ofcourse)
 
 
 You can find all the SAS error codes in the ErrorCode.java class
 You can find all the SAS error codes in the ErrorCode.java class