User authorization - Revision history

Adminwiki: 10 revisions imported

2021-05-07T08:07:33Z

10 revisions imported

← Older revision	Revision as of 08:07, 7 May 2021
(No difference)

w>Mpolo: bringback url

2010-10-15T07:48:15Z

bringback url

← Older revision		Revision as of 07:48, 15 October 2010
Line 41:		Line 41:
	[[File:Userauth.png\|none\|Application authorization page]]		[[File:Userauth.png\|none\|Application authorization page]]

	Once the user authorizes your application, he is then redirected to the [[~~user~~ bringback url]] as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.		Once the user authorizes your application, he is then redirected to the [[bringback url]] as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.

	= Authorization state =		= Authorization state =
	You can query whether an authkey has been authorized using the [[authkey.state]] component. This component returns the current auth key status and the current [[nonce key]] to use in some funcion calls.		You can query whether an authkey has been authorized using the [[authkey.state]] component. This component returns the current auth key status and the current [[nonce key]] to use in some funcion calls.

w>Jguillo at 12:06, 4 May 2010

2010-05-04T12:06:00Z

← Older revision		Revision as of 12:06, 4 May 2010
Line 44:		Line 44:

	= Authorization state =		= Authorization state =
	You can query an authkey ~~state~~ using the [[authkey.state]] component. This component returns the current auth key status and the current nonce key to use in some funcion calls.		You can query whether an authkey has been authorized using the [[authkey.state]] component. This component returns the current auth key status and the current [[nonce key]] to use in some funcion calls.

	~~Some security-risk operations such as the creation or modification of a work registration require a '''nonce key''' which is changed every time it's used in such operations~~.

w>Jguillo at 11:47, 4 May 2010

2010-05-04T11:47:09Z

← Older revision		Revision as of 11:47, 4 May 2010
Line 13:		Line 13:

	== Creating an authkey ==		== Creating an authkey ==
	In order to create an authKey you must use [[~~authkey.create component\|~~authkey.create]]. That function return a new authKey and its associated private key.		In order to create an authKey you must use [[authkey.create]]. That function return a new authKey and its associated private key.

	'''IMPORTANT:''' You must save the authkey's private key for future use. It cannot be obtained again anywhere. If you lose an authkey's private key you will be forced to create a new authkey for the user.		'''IMPORTANT:''' You must save the authkey's private key for future use. It cannot be obtained again anywhere. If you lose an authkey's private key you will be forced to create a new authkey for the user.
Line 44:		Line 44:

	= Authorization state =		= Authorization state =
	You can query an authkey state using the [[authkey.state ~~component~~]]. This component returns the current auth key status and the current nonce key to use in some funcion calls.		You can query an authkey state using the [[authkey.state]] component. This component returns the current auth key status and the current nonce key to use in some funcion calls.

	Some security-risk operations such as the creation or modification of a work registration require a '''nonce key''' which is changed every time it's used in such operations.		Some security-risk operations such as the creation or modification of a work registration require a '''nonce key''' which is changed every time it's used in such operations.

w>Jguillo at 11:20, 4 May 2010

2010-05-04T11:20:14Z

← Older revision		Revision as of 11:20, 4 May 2010
Line 41:		Line 41:
	[[File:Userauth.png\|none\|Application authorization page]]		[[File:Userauth.png\|none\|Application authorization page]]

	Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.		Once the user authorizes your application, he is then redirected to the [[user bringback url]] as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.

	= Authorization state =		= Authorization state =

w>Jguillo at 11:18, 4 May 2010

2010-05-04T11:18:33Z

← Older revision		Revision as of 11:18, 4 May 2010
Line 39:		Line 39:
	User will be asked to log in Safe Creative and be presented with a page like this:		User will be asked to log in Safe Creative and be presented with a page like this:

	[[File:Userauth.png]]		[[File:Userauth.png\|none\|Application authorization page]]

	Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.		Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.

w>Jguillo at 11:14, 4 May 2010

2010-05-04T11:14:52Z

← Older revision		Revision as of 11:14, 4 May 2010
Line 9:		Line 9:
	* MANAGE level allows modification and deletion of registered works		* MANAGE level allows modification and deletion of registered works

	= Creating an authkey =		= Obtaining a user's authorization =
			Getting a user's authorization for your application is a two-step operation. First you must create an authkey and then you must redirect the user to a special page to activate that authkey

			== Creating an authkey ==
	In order to create an authKey you must use [[authkey.create component\|authkey.create]]. That function return a new authKey and its associated private key.		In order to create an authKey you must use [[authkey.create component\|authkey.create]]. That function return a new authKey and its associated private key.

	'''IMPORTANT:''' You must save the authkey's private key for future use. It cannot be obtained again anywhere. If you lose an authkey's private key you will be forced to create a new authkey for the user.		'''IMPORTANT:''' You must save the authkey's private key for future use. It cannot be obtained again anywhere. If you lose an authkey's private key you will be forced to create a new authkey for the user.

	= User authorization of an authkey =		== User authorization of an authkey ==

	Once created you must link the authkey to a user by redirecting the user to the <tt>/api-ui/authkey.edit</tt> page:		Once created you must link the authkey to a user by redirecting the user to the <tt>/api-ui/authkey.edit</tt> page:

w>Jguillo at 11:12, 4 May 2010

2010-05-04T11:12:42Z

@@ Line 41: / Line 41: @@
 = Authorization state =
-You can query an authkey state using
+You can query an authkey state using the [[authkey.state component]]. This component returns the current auth key status and the current nonce key to use in some funcion calls.
-REQUEST:
+Some security-risk operations such as the creation or modification of a work registration require a '''nonce key''' which is changed every time it's used in such operations.

w>Jguillo at 11:10, 4 May 2010

2010-05-04T11:10:23Z

← Older revision		Revision as of 11:10, 4 May 2010
Line 35:		Line 35:

	User will be asked to log in Safe Creative and be presented with a page like this:		User will be asked to log in Safe Creative and be presented with a page like this:

			[[File:Userauth.png]]

	Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.		Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.

w>Jguillo at 10:46, 4 May 2010

2010-05-04T10:46:37Z

← Older revision		Revision as of 10:46, 4 May 2010
Line 18:		Line 18:
	Once created you must link the authkey to a user by redirecting the user to the <tt>/api-ui/authkey.edit</tt> page:		Once created you must link the authkey to a user by redirecting the user to the <tt>/api-ui/authkey.edit</tt> page:

	http://www.safecreative.org/api-ui/authkey.edit?authkey=23j22wtpoguzgzk0fag39sey6&level=GET&sharedkey=zy9x4ol0ctg3btyswq7b5wi9&ztime=1271749822662&signature=f8d9fd7d0b9a9c517d963881a4e8ded03cb2cec5		<pre>
			http://www.safecreative.org/api-ui/authkey.edit
			?authkey=23j22wtpoguzgzk0fag39sey6
			&level=GET
			&sharedkey=zy9x4ol0ctg3btyswq7b5wi9
			&ztime=1271749822662
			&signature=f8d9fd7d0b9a9c517d963881a4e8ded03cb2cec5
			</pre>

	You must provide the following parameters to this page:		You must provide the following parameters to this page:
Line 26:		Line 33:
	* ztime: Server [[ztime]]		* ztime: Server [[ztime]]
	* signature: [[signature parameter\|Parameters signature]] using the authkey's private key		* signature: [[signature parameter\|Parameters signature]] using the authkey's private key

			User will be asked to log in Safe Creative and be presented with a page like this:

	Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.		Once the user authorizes your application, he is then redirected to the bringback url as defined in the userkey. Redirection is automatic when the user already has an authorization of the same level.