Authentication - Revision history

Bzurkovic at 17:08, 29 October 2011

2011-10-29T17:08:16Z

Bzurkovic at 16:50, 21 May 2008

2008-05-21T16:50:24Z

Bzurkovic at 05:41, 9 May 2008

2008-05-09T05:41:49Z

Bzurkovic at 05:40, 9 May 2008

2008-05-09T05:40:35Z

Bzurkovic: New page: == Authentication == Every function of the SOAP API that requires authentication must pass in Authentication Parameters. To acquire a set of Authentication Parameters, please use the AP...

2008-05-09T05:39:37Z

New page: == Authentication == Every function of the SOAP API that requires authentication must pass in Authentication Parameters. To acquire a set of Authentication Parameters, please use the AP...

New page

== Authentication ==

Every function of the SOAP API that requires authentication must pass in Authentication Parameters. To acquire a set of Authentication Parameters, please use the API found at: http://api.upsidewireless.com/soap/Authentication.asmx.

Token and Signature, two values that are returned from the function are then used for every subsequent call to the API. They are used as proxies for your username and password as some users prefer to use the non-SSL optinon for function calls, in which case, calls made to the API are sent over the Internet unencrypted. The use of proxies prevents unauthorized access to your Upside Wireless account.

The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.

@@ Line 4: / Line 4: @@
 Every function of the SOAP API that requires authentication must pass in Authentication Parameters. To acquire a set of Authentication Parameters, please use the API found at: http://api.upsidewireless.com/soap/Authentication.asmx.
-Token and Signature, two values that are returned from the function are then used for every subsequent call to the API. They are used as proxies for your username and password as some users prefer to use the non-SSL optinon for function calls, in which case, calls made to the API are sent over the Internet unencrypted. The use of proxies prevents unauthorized access to your [http://reseller.upsidewireless.com/ Upside Wireless] account.
+Token and Signature, two values that are returned from the function are then used for every subsequent call to the API. They are used as proxies for your username and password as some users prefer to use the non-SSL option for function calls, in which case, calls made to the API are sent over the Internet unencrypted. The use of proxies prevents unauthorized access to your [http://reseller.upsidewireless.com/ Upside Wireless] account.
-The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.
+The Token parameter will never change for the life of the account whereas the Signature will change if your password changes.
-'''WARNING (NOT THE USUAL YADDA, YADDA):''' If you change your password in your on-line account, you must visit [[http://api.upsidewireless.com/soap/Authentication.asmx http://api.upsidewireless.com/soap/Authentication.asmx]] to have token/signature re-issued.
+'''WARNING (NOT THE USUAL YADDA, YADDA):'''

← Older revision		Revision as of 16:50, 21 May 2008
Line 7:		Line 7:

	The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.		The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.
		+
		+	'''WARNING (NOT THE USUAL YADDA, YADDA):''' If you change your password in your on-line account, you must visit [[http://api.upsidewireless.com/soap/Authentication.asmx http://api.upsidewireless.com/soap/Authentication.asmx]] to have token/signature re-issued.
		+

← Older revision		Revision as of 05:41, 9 May 2008
Line 7:		Line 7:

	The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.		The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.
		+
		+
		+
		+	----
		+	[[APIs \| back]]

@@ Line 1: / Line 1: @@
 == Authentication ==
@@ Line 5: / Line 4: @@
 Every function of the SOAP API that requires authentication must pass in Authentication Parameters. To acquire a set of Authentication Parameters, please use the API found at: http://api.upsidewireless.com/soap/Authentication.asmx.
-Token and Signature, two values that are returned from the function are then used for every subsequent call to the API. They are used as proxies for your username and password as some users prefer to use the non-SSL optinon for function calls, in which case, calls made to the API are sent over the Internet unencrypted. The use of proxies prevents unauthorized access to your Upside Wireless account.
+Token and Signature, two values that are returned from the function are then used for every subsequent call to the API. They are used as proxies for your username and password as some users prefer to use the non-SSL optinon for function calls, in which case, calls made to the API are sent over the Internet unencrypted. The use of proxies prevents unauthorized access to your [http://reseller.upsidewireless.com/ Upside Wireless] account.
 The Token parameter will never change for the life of the account whereas the Signature will change if your password changes. In most applications, you will store these variables in a constant or configuration store.