Authentication

About

this article discusses how to perform remote authentication using your i4a website and data from a remote website or program. It's important to note that the remote process need NOT be a website, it could be an application, even a mobile app or mobile website.

Requirements

• SOAP. The authentication protocol currently utilizes SOAP. This is the mechanism that the i4a website uses to provide authentication. This is a common protocol, with broad support and a lot of online resources that can provide both education as well as support for this.
• A dedicated admin i4a account to use for this.
• The GUID token that is unique for each i4a website. This value can be obtained by logging into your site admin, then choosing 'Site Stats' from the Admin dropdown menu. Within that page is a value labeled 'GUID'. Your vendor will need this value to use the authentication routines.

Use

• To access the authentication routine, your vendor must first authenticate themselves. You could think of this as an initial handshake so that both parties can then begin further communication.