Protocols/WebAPI/Auth: Difference between revisions

Latest revision as of 22:49, 25 March 2020

@@ Line 1: / Line 1: @@
 {{Protocols/WebAPI}}
-Desktop clients usually want to authenticate users and obtain security tokens that they can use to access other Services on behalf of the users. A typical example is an desktop instant messaging client trying to authenticate a user and connect to the user's Instant messaging service to send and receive messages.
-NINA OpenAuth APIs provide a new method called "clientLogin", to allow clients to authenticate NINA/AIM/ICQ users securely and obtain an authentication token that can be used to access NINA Open Services like [[Protocols/WebAPI/Clients#WebAIM|WebAIM]].
-As illustrated in the diagram below, this can be done using NINA OpenAuth Service in 2 steps - authenticate the user using the "clientLogin" request and then make a Service Request on behalf of the user using the security token obtained from the "clientLogin" request.
@@ Line 13: / Line 6: @@
 [[Category:AIM]]
 [[Category:Protocols/WebAPI]]
+[[Category:Protocols/WebAPI/Auth]]
+[[Category:Protocols/WebAPI/Auth/Client]]
 [[Category:Work_In_Progress]]