> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/user-guide/monitoring/sap/netweaver/j2ee-system/keystore-views-and-certificates-monitoring.md).

# Keystore Views and Certificates Monitoring

SAP AS Java manages certificates and cryptographic keys through a Key Storage service, organizing them into multiple virtual containers known as Keystore Views. These views serve as the foundation for core security operations, including encryption, digital identification, and signature verification, across AS Java functions. Underlying each view is a distributed database where the actual key and certificate entries are persisted.

IT-Conductor simplifies the oversight of these assets by providing automated discovery and threshold-based monitoring of Keystore Views and their certificates from a single platform.

### Permissions <a href="#keystoreviewsandcertificatesmonitoring-permissions" id="keystoreviewsandcertificatesmonitoring-permissions"></a>

To enable IT-Conductor to monitor keys and certificates, ensure the required roles and permissions are configured before proceeding.

1. [Sign in to IT-Conductor](https://service.itconductor.com/) and on the main menu navigate to [**Support > Downloads > SAP Security Downloads**](https://service.itconductor.com/objectSavedSearch?OBJECT_Id=5930548857087850\&itconductor.menuItem=5930548857087850) and download the **SAP J2EE Monitoring Role**. This role has high-level monitoring permissions and includes access to the **keystore/keystore-views** action, which governs access to Keystore View discovery.
2. Assign the **SAP J2EE Monitoring Role** to an SAP user designated for monitoring.

<figure><img src="https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FbMCu7550LAOxHCEjiagE%2Froles.png?alt=media&amp;token=75b3fe9b-1117-4569-9b4a-5ab27d3dd462" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note:** Learn more about the [SAP J2EE Monitoring Role](https://docs.itconductor.com/user-guide/monitoring/sap/netweaver/j2ee-system/monitoring-role) in our documentation.
{% endhint %}

![Figure 2: ITCONDUCTOR\_MONITORING Assigned Actions View in Detail](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FcV2jaw4Gm1HdBlfWdFqi%2FKeystore%20assigned%20action.png?alt=media\&token=87bfcf95-c9e1-49ec-b726-63b5fa57db2f)

3. Grant access to individual certificates by assigning specific actions as needed. For example: Monitoring the certificates in **SecureLoginServer** keystore view:

![Figure 3: Sample SecureLoginServer View in Detail](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FDo5gEOe9TQmSkzXixGzD%2FSecureLoginServer.png?alt=media\&token=10e04baf-f773-48e4-a048-44a73028c997)

4. Assign the required permissions to the designated monitoring user by creating a new role **ITCONDUCTOR\_CERTIFICATES** with the following actions:
   1. **keystore-view\.SecureLoginServer / view-actions.all.all**
   2. **keystore-view\.SecureLoginServer / entry-actions.all.all**

![Figure 4: Sample ITCONDUCTOR\_CERTIFICATES View in Detail (a)](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FmyAkVey2CHFfN39BcRiP%2FCertificates.png?alt=media\&token=a26b34fc-5920-4348-90a0-409e05afba4d)

5. Repeat step #4 for all views that require their certificates to be monitored:
   1. **keystore-view.\<View Name> / view-actions.all.all**
   2. **keystore-view.\<View Name> / entry-actions.all.all**

![Figure 5: Sample ITCONDUCTOR\_CERTIFICATES View in Detail (b)](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2Fut7hk6wMdDORQZy6Mz9t%2FCertificates\(2\).png?alt=media\&token=593cf809-6744-4582-92fe-d8fdbb74d0ff)

6. Assign the newly created role **ITCONDUCTOR\_CERTIFICATES** to the designated monitoring user.

#### Validation

Confirm the configuration is correct by verifying the following:

* Verify that the monitoring role has been updated with the required actions for the relevant Keystore Views and certificate entries.
* Confirm that the monitoring user can access the relevant monitoring sections in NWA.
* Confirm that the monitoring user can open the respective Keystore Certificate entries without any access-denied or runtime errors.
* Ensure that permissions are granted explicitly for each Keystore View, rather than through wildcard permissions.

After performing all these steps, IT-Conductor will discover and start monitoring individual certificates under the Key Store

![Figure 6: Sample Individual Certificates](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2Fv6pXjILH5jdtAHyIwRoO%2FSample%20Individual%20Certificates.png?alt=media\&token=fbf1aa43-13d8-41d8-8e2c-d1a0c0dfe0fc)

{% hint style="info" %}
**Note:** This is the only way SAP allows granting access to individual certificates. Although IT-Conductor only requires READ access, there are no such actions configured out-of-the-box by SAP. If your organization has qualified SAP J2EE developers, they can create custom actions to grant only READ access in SAP Java Studio and install them into the system. These actions can be assigned to the ITCONDUCTOR\_CERTIFICATES role instead of view-actions.all.all/ entry-actions.all.all
{% endhint %}

### Monitoring keys and certificates in IT-Conductor <a href="#monitoring-keys-and-certificates-in-it-conductor" id="monitoring-keys-and-certificates-in-it-conductor"></a>

IT-Conductor automatically discovers all Keystore Views and any certificates within views where the monitoring user has access. From there, you can configure thresholds to track **Keystore View status** as well as **Certificate Expiration** and **Days to Expiration**.

#### Key Monitoring Metrics <a href="#key-monitoring-metrics" id="key-monitoring-metrics"></a>

* **Keystore View Status** — The overall health state of a Keystore View, calculated by SAP as the "worst of" status across all entries it contains.
* **Certificate Expiration** — The date on which a certificate becomes invalid and can no longer be trusted.
* **Days to Expiration** — The number of days remaining before a certificate reaches its expiration date.

![Figure 1: Sample Keystore Views and Certificates](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FPtZoe8MgUYJ7Crp1VPk0%2FKeystore%20views.png?alt=media\&token=17b3da16-14b6-4acd-b960-5fd764975fea)

### Related Information <a href="#keystoreviewsandcertificatesmonitoring-moreinformation" id="keystoreviewsandcertificatesmonitoring-moreinformation"></a>

* [SAP PO Application Monitoring](https://docs.itconductor.com/user-guide/monitoring/sap/netweaver/j2ee-system/po-application-monitoring.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.itconductor.com/user-guide/monitoring/sap/netweaver/j2ee-system/keystore-views-and-certificates-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
