• Secure authentication,
• Authorizations,
• Access tokens and refresh tokens,
• Scopes (permissions associated with a token).

1. Installing an HFSQL server on the web server.
2. Installing WEBDEV Application Server and choosing BaaS services.
3. Launching the BaaS administration site and creating OAuth credentials.

Prerequisite: Installing an HFSQL server

Installing WEBDEV Application Server

1. Select the installation language of WEBDEV Application Server and confirm.
2. Select "Install full version" and enter the activation key. Proceed to the next step of the wizard.
3. Accept the license agreement. Proceed to the next step of the wizard.
4. Select the installation directory ("C:\WEBDEV" by default).
5. Select the WEBDEV Application Server mode:
   • To install a standard WEBDEV Application Server, select "Stand-alone server".
   • To install a WEBDEV server cluster, select "Cluster".
   Select "Stand-alone server" and proceed to the next step of the wizard.
6. This step allows you to specify the root directory for deploying websites and web services. Keep the default path and proceed to the next step.
7. If it is the first time you install WEBDEV Application Server, specify the parameters of the Windows account that will be used as WEBDEV administrator. This account will also be called "Hosting account".
   You can create a new Windows account or use an existing Windows account.
   
   
   Select an option and proceed to the next step.
8. If a previous version of WEBDEV Application Server has already been installed on the computer, the wizard allows you to:
   • manage the websites and web services from earlier versions. Keep the "Keep sites in their current versions" option and proceed to the next step.
   • import WEBDEV accounts. Keep the option "Don't import existing accounts" and proceed to the next step. Enter the login credentials of the Windows account that will be used as WEBDEV administrator. This account will also be called "Hosting account".
     You can create a new Windows account or use an existing Windows account.
     Select an option and proceed to the next step.
9. This step allows you to enable remote administration sites:
   • WEBDEV Application Server administration site.
   • HFSQL administration site.
10. The next step allows you to manage the hosting of SaaS websites. The SaaS activation automatically installs a website and a web service to manage your SaaS websites. For more details, see SaaS. Validate this step.
11. The following steps allow you to enable replication and telemetry functionalities. You can enable these functionalities later, in the WEBDEV Application Server administrator.
    In our case, this server is not required. Keep the default option.
12. The next step is to enable BaaS services to manage users, authentication and a Private Store.
    In our case, select "Enable BaaS". Go to the next step.
13. Specify the characteristics of the HFSQL server used for the BaaS service.
    Note: This HFSQL server must have been previously installed (see prerequisites).
    
    These characteristics are:
    • Name of the HFSQL server,
    • Port.
    • Name and password of the HFSQL server administrator. This information is required to automatically configure the WDBaaS database and the associated user.
14. Click "Test connection" to check your connection parameters.
15. Specify the parameters specific to the WDBaaS database used for the User Groupware/Private Store/OAuth authentication:
    • name of the dedicated database: WDBAAS by default.
    • username and password for the database.
16. Specify the password for the WDBaaS data files (existing or to be created).
17. Specify the password of the WDBaaS site administrator (User: Admin).
18. This database and its user will be automatically created.
19. Go to the next step.
20. In this next step, you can enable access to third-party databases.
    In our case, this access is not required. Keep the default option.
21. Specify whether an SSL connection is required for the remote administration sites.
22. In the next step, specify whether the ODBC driver is to be installed.
23. The next step allows you to enable advanced settings.
24. Go to the next step.
25. The setup summary is displayed.
26. Go to the next step.
27. The wizard checks for a web server on the setup computer.
    • If no web server is installed on the setup computer, the wizard prompts you to install and configure one to use WEBDEV Application Server.
    • If there is a web server on the computer, the wizard configures it so that you can use WEBDEV Application Server.
28. At the end of the setup, the wizard displays a summary:
    
    WDBaaS server connection token to be provided to the environment development:
    WDXxxxxxxxxxxxxxxxxxxxxx
    
    HFSQL account to be used so that the site and the WDBaas web service can access the HFSQL server:
    - Server: xxx
    - Database: xxx
    - User xxx - Password: xxx
    
    File password: xxx
    
    WDBaaS site administrator password (User: xxx): xxxx
    
    Keep this information. The token to connect to the WDBaaS server must be used:
    • in the User Groupware settings window in your WINDEV project.
    • in the User Groupware / Private Store settings window in your WINDEV Mobile project.
    • in the User Groupware configuration window in your WEBDEV project.
29. Finish the wizard. You can directly launch the WDBaaS administration site of the Private Store.

Warning
Even if you only use the OAuth functionality, it is advisable to keep all this information. It will be required if you use the Private Store.

Opening the Private Store website

1. Open the Private Store: http(s)://ComputerName/WDBAAS.
   
   Warning
   The Private Store is opened by specifying the computer name (or IP address) and not "localhost".
2. Click "Log in".
3. Enter the WDBAAS administrator login credentials. This information was provided at the end of the WEBDEV Application Server installation.
4. Click "Administration".
5. Go to the "OAuth 2.0 server" tab.

Creating OAuth 2.0 credentials

1. Click the "Create your first OAuth 2.0 credentials" link (or click the "Add credentials" button in the "OAuth 2.0 credentials" tab if you have already created credentials).
2. The OAuth 2.0 credential configuration page appears. This page has 2 tabs:
   • General options: Allows you to define the parameters of the credentials to be created.
   • Login page: Defines the user login page (when a "User" token is used).
   By default, new tokens are created as User tokens. They can be transformed into Application tokens.
3. The characteristics of the credentials are automatically generated in the "General options" tab. These include Client ID, Client Secret and creation date.
4. Complete the details of the credentials:
   • Name of credentials. This name will simplify the search in the list of credentials.
   • Connection authorization. If the credentials are active, they can be used for testing and production purposes
   • One or more redirect URLs. By default: http://localhost:9874
   • Token lifetime (10 days by default).
   • Optional description.
   • Indicate whether the new token is a user token or an application token.
     In the case of a user token, you can define the login page.
   • Indicate whether SSO is available for these credentials.
5. Copy the Client ID and Client Secret information, as they will be required in the client application when a token is requested.
6. Click "Save" to create the credentials. A summary page appears with the various URLs required to request a token from the client application.

Creating APIs for web services

1. Click the "Create your first API for web services" link (or click the "Add an API" button in the "APIs for web services" tab if you have already created APIs).
2. Enter the details of the API entry point:
   • Name
   • API URL,
   • Optional description.
3. Add the necessary scopes.
   Note: Scopes are described in APIs. They are used to filter functionalities according to the credentials.
4. Click "Save" to create the API.
5. Click the "OAuth 2.0 credentials" tab.
6. Edit the OAuth 2.0 credentials you want to associate with the API.
7. Click the "APIs" tab.
8. Select the APIs to which the client application will have access.
9. Click "Save".

Scopes

• "openid": verifies user identity.
• "profile": gets the user's name.
• "email": gets the user's email address.

"Application" token

AuthParam is OAuth2Parameters
tok is AuthToken

AuthParam.ClientID = "b18b7850-8f4a-4d2a-9ee2-309876b36ba6"
AuthParam.ClientSecret = "4b3e99d8-b736-430e-a780-cb1586927e2d"
AuthParam.AuthURL = "http://doc-7/oauth2/v1/authorize"
AuthParam.TokenURL = "http://doc-7/oauth2/v1/token"
AuthParam.RedirectionURL = "http://localhost:9874"
AuthParam.GrantType = gtClientCredentials

tok = AuthIdentify(AuthParam)
IF ErrorOccurred THEN
	Error(ErrorInfo())
ELSE
	Info(tok.Value, tok.ExpirationDate)
END

"User" token

AuthParam is OAuth2Parameters
tok is AuthToken

AuthParam.ClientID = "b18b7850-8f4a-4d2a-9ee2-309876b36ba6"
AuthParam.ClientSecret = "4b3e99d8-b736-430e-a780-cb1586927e2d"
AuthParam.AuthURL = "http://doc-7/oauth2/v1/authorize"
AuthParam.TokenURL = "http://doc-7/oauth2/v1/token"
AuthParam.RedirectionURL = "http://localhost:9874"

tok = AuthIdentify(AuthParam)
IF ErrorOccurred THEN
	Error(ErrorInfo())
ELSE
	Info("Token value " + tok.Value, "Expiration date "+ tok.ExpirationDate)
	MyIdentity is OpenIDIdentity = OpenIDReadIdentity(tok)
	IF MyIdentity.Valid THEN
		Trace("Email address: " + MyIdentity.Email)
		Trace("Last name:" + MyIdentity.LastName)
		Trace("First name: " + MyIdentity.FirstName)
	END
END

openIDparam is OpenIDParameters

openIDparam.ClientID = "8351ea5f-19b6-4789-87ea-6ba01a3dffd2"
openIDparam.ClientSecret = "597fcab9-f76d-4555-abdb-06adcfeaf7d8"
openIDparam.ConfigurationURL = "http://doc-7/.well-known/openid-configuration"
openIDparam.RedirectionURL = "http://localhost:9874"
openIDparam.GrantType = gtAuthorizationCode

tok = AuthIdentify(openIDparam)
IF ErrorOccurred THEN
	Error(ErrorInfo())
ELSE
	Info(tok.Value, tok.ExpirationDate)
END