AlphaKey

Overview

Integrating Logpresso Sonar with AlphaKey provides two capabilities.

• SSO login: Users sign in to Sonar with their AlphaKey account over SAML 2.0. In this integration Sonar acts as the SP (Service Provider) and AlphaKey acts as the IdP (Identity Provider).
• Audit log collection: AlphaKey SSO/IAM audit events are delivered to Sonar and stored. AlphaKey pushes the logs to Sonar.

The two capabilities are independent — you can use only SSO, or only log collection. Settings are entered on both the AlphaKey and the Sonar side, and each side needs a value produced by the other, so follow the order below.

1. Register the app in AlphaKey and enter the Sonar address.
2. Enter the IdP information issued by AlphaKey into the Sonar SSO configuration.
3. Activate and test the integration in AlphaKey → Sonar order.
4. Add a logger in Sonar, then set its receiving address as the log forwarding target in AlphaKey.

Scope

Requirements

AlphaKey app registration

Register the Logpresso app in AlphaKey and enter the integration information. The IdP information issued in this step becomes the input for the Sonar SSO configuration.

Step 1: Add the app

In the AlphaKey administrator page, go to AlphaKey > 앱 (App) > 앱 현황 (App Status) and click 앱 추가 (Add App).

Under 앱 추가 방식 선택 (Select how to add the app), choose AlphaKey에 등록된 앱 추가 (Add an app registered in AlphaKey) and click 다음 (Next).

Search for Logpresso, select the app, and click 적용 (Apply).

Enter the contract information to create the app integration page.

Step 2: Enter the integration information

Enter the Sonar address on the app integration page that was created.

Example values.

Client page  : https://sonar.example.com
Redirect URL : https://sonar.example.com/sso/alphakey-saml2
Entity ID    : https://sonar.example.com

Step 3: Check the IdP information

After entering the values, click IDP 정보 보기 (View IDP information). The values on the 기본정보 (Basic information), Meta data, and 인증서 PEM (Certificate PEM) tabs are entered into Sonar in the next step, so keep the window open.

Logpresso SSO configuration

Go to System > SSO, click Add, and enter the values shown on the AlphaKey app integration page and the IDP 정보 (IDP information) window as follows.

The ACS URL and SP Entity ID must match the redirect URL and entity ID entered in AlphaKey exactly, character for character.

For the SSO URL, enter the Location address of the SingleSignOnService element on the Meta data tab.

For the IdP Entity ID, enter the issuer (IDP entity ID) on the 기본정보 (Basic information) tab.

For the X.509 certificate, copy only the Base64 body from the 인증서 PEM (Certificate PEM) tab, excluding the BEGIN CERTIFICATE and END CERTIFICATE lines.

Activating the integration

Once the values are entered on both the AlphaKey and the Sonar side, activate the integration in the following order.

Click 적용 (Apply) in AlphaKey, then click Save in Sonar.

Next, turn on the Enabled switch for the registered AlphaKey SAML 2.0 entry in the Sonar SSO list. In AlphaKey, click 연결테스트 (Connection test) and confirm that the Sonar login screen is called.

If the connection test succeeds, click 연동 (Integrate). The SSO integration is complete once the Logpresso app appears in the AlphaKey 앱 현황 (App Status) list.

Logpresso collection configuration

AlphaKey pushes its audit logs directly to Sonar. Create the receiving logger in Sonar first — the callback name you set there determines the receiving address.

Step 1: Add a logger

Go to Collect > Loggers, click Add, and enter the following values.

Step 2: Set the AlphaKey log forwarding target

In the AlphaKey administrator page, set the audit log forwarding target as follows.

Example forwarding address.

https://sonar.example.com/log/alphakey

Post-installation verification

Verifying SSO login

Check that AlphaKey SAML 2.0 login has been added to the Sonar login screen, then sign in with an AlphaKey account.

• Success: You are authenticated by AlphaKey and signed in to Sonar.
• Failure: If a signature verification error occurs, check that the X.509 certificate does not include the BEGIN/END lines, and that the redirect URL and the ACS URL are identical.

Verifying log collection

Run the query below to confirm that collection actually works. Replace ALPHAKEY_AUDIT with the table name you entered on the logger.

table duration=10m ALPHAKEY_AUDIT
| stats count

• Success: The number of records collected within the last 10 minutes is 1 or more.
• Failure: If it is 0, re-check the AlphaKey log forwarding settings (host, path), whether the logger callback name matches, and network reachability to the collection node (HTTPS/443 inbound).

Run the query below to confirm that the fields are parsed correctly.

table duration=10m ALPHAKEY_AUDIT
| fields _time, event_type, event_group, user, user_name, src_ip, msg

References

• Logpresso Sonar documentation
• SSO configuration guide
• Logger configuration guide