---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# (Optional) Enable signed logout requests

# (Optional) Enable signed logout requests {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Some IdPs require the Service Provider to sign logout requests with a
certificate.

## Vorbereitungen

Role required: sso_config_admin, business_rule_admin, script_include_admin

## Warum und wann dieser Vorgang ausgeführt wird

If your IdP requires signed logout requests, use the IdP's metdata to set the
following system properties.

## Prozedur

1. In the Advanced tab, from the property Sign LogoutRequest. Set this property to true if the Identity Provider's SingleLogoutRequest service requires signed LogoutRequest, select Yes to specify that your IdP requires a signed logout request, or select No to use unsigned logout requests.
2. If you selected Yes to Sign LogoutRequest, then in The protocol binding for the Identity Provider's SingleLogoutRequest service. (Value can be either "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" or "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST".) property, enter the one of the supported values listed in `Binding` attribute from the` SingleLogoutService` element.  
   By default, the integration uses an HTTP-Redirect binding.
3. Click Update.
4. [Install a Service Provider (SP) key store](https://servicenow-prod.fluidtopics.net/kQpi6h4VFreZgjE0hG0Veg "Use the following steps to remove the existing example key store and install your own Service Provider key store containing your public and private key pair.").