[DOCS] SAML with Azure Active Directory using outdate API

Open
#2,224 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure
Domain
authentication, documentation

Research direction

Open the linked SAML with Azure AD documentation page and locate the final "Role Mapping" section. Update the outdated role-mapping API example, then review the surrounding Azure AD configuration to determine whether the example should use the user's principal or an Active Directory group and verify the rendered documentation.

Written by the indexing model from the issue text.

Description

This page the last section for Configure SAML with Azure AD to access Kibana that discusses "Role Mapping" has an example that leverages an outdate API. Instead of POST /_xpack/security/role_mapping/SAML_kibana, the API should be POST /_security/role_mapping/SAML_kibana

This example could be made more complete by showing how to create a role against an Active Directory group rather than <firstname.lastname> which I don't believe is a default returned from Azure AD into our Name field. By default, I believe its the user's principal, which based upon the example configurations above would be the users email address.

image
Dominant language
Java
Stars
105
Forks
249
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/stack-docs

All issues in elastic/stack-docs

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.