Interfaces used by SCEP clients to request SCEP related operations on top of RA Profile. SCEP Profile defines the behaviour for the specific SCEP configuration. SCEP Profile is bound with specific RA Profile and it can be used by the SCEP clients to request operations on their specific URL. These operations are always specific only for the RA Profile.
| raProfileName required | string |
| operation required | string |
| message | string Base64 encoded CMS data |
{- "type": "notFound",
- "title": "Not Found",
- "detail": "Requested object is not found",
- "subproblems": [
- { }
], - "algorithms": [
- "ES256"
]
}| raProfileName required | string |
| operation required | string |
Binary CMS data
{- "type": "notFound",
- "title": "Not Found",
- "detail": "Requested object is not found",
- "subproblems": [
- { }
], - "algorithms": [
- "ES256"
]
}Interfaces used by SCEP clients to request SCEP related operations. SCEP Profile defines the behaviour for the specific SCEP configuration. When the SCEP Profile contains default RA Profile, it can be used by the SCEP clients to request operations on their specific URL.
| scepProfileName required | string |
| operation required | string |
| message | string Base64 encoded CMS data |
{- "type": "notFound",
- "title": "Not Found",
- "detail": "Requested object is not found",
- "subproblems": [
- { }
], - "algorithms": [
- "ES256"
]
}| scepProfileName required | string |
| operation required | string |
Binary CMS data
{- "type": "notFound",
- "title": "Not Found",
- "detail": "Requested object is not found",
- "subproblems": [
- { }
], - "algorithms": [
- "ES256"
]
}