Skip to content

Commit a75a4db

Browse files
BigPandaToolcawl
andcommitted
Adding information about SAML API to SAML guide (elastic#66404)
* Adding information about SAML API to SAML guide Adding information about new SAML metadata API to SAML guid Related:#elastic#49018 Co-authored-by: lcawl <[email protected]>
1 parent d9f56cf commit a75a4db

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

x-pack/docs/en/security/authentication/saml-guide.asciidoc

+13-5
Original file line numberDiff line numberDiff line change
@@ -614,11 +614,19 @@ Some Identity Providers support importing a metadata file from the Service
614614
Provider. This will automatically configure many of the integration options
615615
between the IdP and the SP.
616616

617-
The Elastic Stack supports generating such a metadata file using the
618-
`bin/elasticsearch-saml-metadata` command in your {es} directory.
619-
620-
The <<saml-metadata,documentation for the elasticsearch-saml-metadata utility>>
621-
describes how to run it, and the available command line options.
617+
The {stack} supports generating such a metadata file using the
618+
<<saml-metadata,`bin/elasticsearch-saml-metadata` command>> or the
619+
<<security-api-saml-sp-metadata,SAML service provider metadata API>>.
620+
621+
You can generate the SAML metadata by issuing the API request to {es} and store
622+
it as an XML file using tools like `jq`. For example, the following command
623+
generates the metadata for the SAML realm `realm1` and saves it to a
624+
`metadata.xml` file:
625+
626+
["source","console"]
627+
--
628+
curl -u user_name:password -X GET http://localhost:9200/_security/saml/metadata/saml1 -H 'Content-Type: application/json' | jq -r '.[]' > metadata.xml
629+
--
622630

623631
[[saml-role-mapping]]
624632
=== Configuring role mappings

0 commit comments

Comments
 (0)