# Enable Basic Auth

yCrash provides Single Sign on capability by integrating with your current corporate SAML solution providers (like OKTA, Active Directory, ....). However, if there are challenges in integrating with your SAML solution, yCrash also provides a basic authentication solution.

You can enable basic authentication by following the steps given here:

  1. You need to create two instances of the yCrash server:

a) yCrash Dashboard instance

b) yCrash Receiver instance

yCrash Dashboard instance is the instance where your users will be accessing the yCrash reports from their browser.

yCrash Receiver instance is the instance where yc-360 script will be transmitting the captured artifacts from your production servers to yCrash server.

You will need to enable basic authentication only on the yCrash Dashboard instance by following the steps given below. In the yCrash receiver instance, you don't have to enable the basic authentication. Because yc-360 script already authenticates to yCrash server through API key. Two levels of authentication are unnecessary.

NOTE: If you are running two instances of yCrash server, then you need to have a common storage for both the server instances.

  1. Edit the yCrash Dashboard instance's 'launch-yc-server.sh' (if you are running yCrash server in Unix) or 'launch-yc-server.bat' (if you are running yCrash server in Windows) and add the following parameters:

--enable-basic-auth --basic-auth-user {YOUR_USER_NAME} --basic-auth-pw {YOUR_PASSWORD}

Say if you want to keep your username as 'ycUser' and password as 'ycPassword' then your launch-yc-server.sh file should look like this:

java ... --enable-basic-auth --basic-auth-user ycUser --basic-auth-pw ycPassword --port 8080 yc.war &
1
  1. From this point, when you anyone tries to open yCrash application in the browser, they will be presented with the username/password authentication challenge:

img