Skip to main content

eBA MIS & MailServer OAuth2 Settings

  1. The "OAuthConfig.json" file in the Common directory is populated with the information from the relevant provider.

  1. The OAuthLogin in the Common directory starts .exe application. If you are working for Microsoft; Run After receiving the token, you can also log in with the system user for schedule tasks and get a token.æ

2.1. To be able to start with the system user; • https://learn.microsoft.com/en-us/sysinternals/downloads/psexec the PsExec tool or https://download.sysinternals.com/files/PSTools.zip and Copied under "C:\Windows\System32\". • Command prompt (cmd.exe) can be opened with admin privilege and "psexec -i -s ......\Common\OAuthLogin.exe" and the OAuthLogin application starts. (Dots The part indicated by represents the place where the midwife is installed)

  1. Navigate with the arrow keys, select the provider used and perform the verification steps. 3.1. Google: An account selection and verification screen will open. After the verification steps are completed, the token the purchase process is carried out. "Received verification code...." page after seeing the message Closed. If desired, the token file can be checked via "C:\ProgramData\Bimser".

3.2. Microsoft: A message will appear with a login url and device code. Navigate to the relevant url and select the given device After the code is entered, the verification steps are completed and the token process is performed. "You have signed in...." The page may be closed after the message is seen. "C:\ProgramData\Bimser" if requested The token file can be checked via .

  1. After the token acquisition is successfully completed, the OAuthLogin.exe application can be closed.
  2. To ensure the sending of e-mails; 5.1. After the required fields on the Mail Settings tab in eBA Configuration Manager are filled in The UseOAuth option is enabled. The fields required by the respective provider are filled in and the application Saved

5.2. Open the MailServer/Profiles/EBA key from the Advanced tab and enter the OAuth information of the respective provider is checked and the necessary parameters are added. 5.2.1. Google: ClientId, ClientSecret and Scopes must be filled in as follows.

5.2.2. Microsoft: ClientId, TenantId, Scopes, Instance, and RedirectUri information as follows must be full.

5.3. The application is registered. Test sending mail via MailServer.exe or Schedule Tasks Be.

  1. For mail reading process; 6.1. The Add profile screen opens from the Mail Integration tab in eBA Configuration Manager and after the required fields are filled, the UseOAuth option is activated. Of the respective provider The required fields are filled in and the application is saved.

6.2. Open the MailServer/Inboxes key from the Advanced tab and select the OAuth information on the relevant profile is checked and the necessary parameters are added. 6.2.1. Step 5.2.1 is applied as follows.

6.2.2. Step 5.2.2 applies as follows.

6.3. The application is registered. The process of reading e-mail can be tested through Schedule Tasks.