5.4.1.2 OcnrfAccessTokenCurrentKeyIdInvalidDetails
Table 5-63 OcnrfAccessTokenCurrentKeyIdInvalidDetails
| Field | Details |
|---|---|
| Description | 'AccessToken request(s) have been rejected by OCNRF (current value is: {{ $value }})' |
| Summary | 'kubernetes_namespace: {{$labels.kubernetes_namespace}},nrflevel:{{$labels.NrfLevel}}, podname: {{$labels.kubernetes_pod_name}}, KeyType: {{$labels.KeyType}}, RejectionReason: {{$labels.RejectionReason}},timestamp: {{ with query "time()" }}{{ . | first | value | humanizeTimestamp }}{{ end }} AccessToken Request has been rejected by OCNRF as CurrentKeyId details are invalid.' |
| Severity | Critical |
| Condition | NRF Access Token Rejected due to token signing details corresponding to CurrentKeyId are invalid. |
| OID | 1.3.6.1.4.1.323.5.3.36.1.2.7034 |
| Metric Used | 'ocnrf_accessToken_tx_responses_total' |
| Recommended Actions | The alert is automatically cleared when NRF receives
Access Token Request, and at that point, Current Key Id details are
invalid. For more information about configuring
currentKeyID parameter, see Oracle Communications Cloud Native Core, Network Repository Function REST
Specification Guide.
|
| Available in OCI | No |