Users management

The notion of user on the OGASYS side depends entirely on the rules specific to each of the installations. An introductory meeting should be scheduled at the beginning of the project to define the appropriate method.

You should know, however, that OGASYS does not keep any password which means that password management, and password changes, must be entirely managed by the service provider Web.

In addition, the process is different for B2B or B2C

B2C authentication process

The normal process for B2C transactions is as follows::

1. The user logs in using their user/password
2. A call must be made to the GET webusers?email={email}&session={session}&options={options} API to determine if the user is valid using the email address
3. If the previous call is successful, the necessary information is retrieved
4. If this is not the case, registration must be carried out.
   
   
   • Request the relevant information (Ex: name, address, etc.)
   • Make a call for creating the user via the API A call must be made to the POST webusers API to determine if the user is valid using the email address
     It should be noted that according to the internal rules determined during the introductory meeting, a customer or delivery address may or may not be created.

B2B authentication process

The normal process for B2B transactions is as follows::

1. Client activation is done at OGASYS level
2. The user logs in using their user/password
3. A call must be made to the GET webusers?email={email}&session={session}&options={options} API to determine if the user is valid using the email address
4. If the previous call is successful, the necessary information is retrieved
5. If this is not the case, the connection is refused. No user creation is done for B2B.