Installation Overview

 

NOTE: It is a good idea to quit the already running application instance of BluwareAuthorizer (BWA) (right-click on the System tray icon and select Quit) before performing an uninstall/upgrade. 

 

 

BluwareAuthorizer is currently supported on Windows and Linux. On Windows, the authorization dialog can be opened in the web browser instead of the BWA built-in browser. To allow this action, perform the following steps:

   1. Stop BWA if already running.

   2. Set the key ba_use_system_browser key to true (set to false by default) in the BluwareAuthorizer/BluwareAuthorizerConfig.ini file in the %AppData%\Bluware\BluwareAuthorizer folder.

   3. Restart BluwareAuthorizer.

 

Note: For enterprise deployment set the environment variable ba_use_system_browser to true in the %AppData%\Bluware\BluwareAuthorizer folder.

 

 

Windows Installation

 

Before installing this version of BWA, uninstall the previous version of BluwareAuthorizer using the following actions:

   1. Stop the running instance of BWA.

   2. Delete BrowserCashe, Database, and Logs folders in the %AppData%\Bluware\BluwareAuthorizer folder. The BluwareAuthorizerConfig.ini file in the %AppData%\Bluware\BluwareAuthorizer folder can be either deleted or updated based on your requirements.

   3. Install the new version of BluwareAuthorizer.

 

BWA can be installed using the MSI installer that will start the Setup Wizard.

 

 

Linux Installation

 

After uncompressing the tar file on Linux, the BluwareAuthorizer folder will contain the BrowserCache, Database, and Logs subfolders.

 

Install using Linux by using the following steps:

 

   1. Extract the provided compressed tar (.tar.gz) file to a known location, typically under /usr/local or under /opt.

       Specify the extracted files directory using the -C option. For example:

   sudo tar -xvzf ~/Downloads/file.tar.gz -C /opt/

 

   2. Run the following script:

   <InstallLocation>/BluwareAuthorizer

 

 

Installing and Running BWA with FAST

 

A config file must be added to the FAST folder at %AppData%\Bluware\FAST (if FAST is run as a desktop application) which will pop up a login page. Users must have the credentials of a registered application to log in with BWA.

 

To install the BluwareAuthorizer to use with FAST, use the following steps after the initial installation:

 

   1. Rename the local BluwareAuthorizer configuration folder:

   $ mv ~/.local/share/BluwareAuthorizer

   ~/.local/share/BluwareAuthorizer-$(date +%Y%m%d-%H%M%S)

 

   2. Run the BluwareAuthorizer from the install folder where it was extracted to, then press ctrl-C to create a new blank configuration file:

   <InstallLocation>$ ./BluwareAuthorizer

   DevTools listening on ws://127.0.0.1:54079/devtools/browser/c61b944c-2741-475c-b768- 8577685eba32

   ^C

   <InstallLocation>$

 

   3. Edit the configuration file and set the license variable by setting the ba_license_path key:

   # license path = Set server location or explicit license file location

   ba_license_path = [email protected]

 

   4. Run BluwareAuthorizer in the background:

   <InstallLocation>$ ./BluwareAuthorizer &

   DevTools listening on ws://127.0.0.1:51582/devtools/browser/f71bfcad-1d5b48d3-a7b6-49

 

   5. Start FAST:

   [BluwareAuthorizer-1.0.0-14-redhat-7]$ sudo systemctl start fast [sudo]

   password for <user>:

 

   6. Try to access the URL:

   sd://opendes/anothersandbox/ST0202R08_VOLVE_POST_STACK_017534_ OPENVDSPLUS001/7A143D27EC88A410

   <InstallLocation>$

   Headless Mode activated

   UI Mode activated

 

   7. After a pause, BluwareAuthorizer will display an Azure sign-in for the repo credentials: