serverless native and realms clarification#5742
Conversation
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
some suggests to make this a little clearer. I think you're tackling this in the right spots
| |-------------------|-------------|--------------------------------|-------------------------| | ||
| | [Security configurations](/deploy-manage/security.md) | Full control | Limited control | Limited control | | ||
| | [Authentication realms](/deploy-manage/users-roles.md) | Available | Available | Available, through {{ecloud}} only | | ||
| | [Authentication realms](/deploy-manage/users-roles.md) | Available | Available | Not available. {{serverless-short}} manages authentication only at the [{{ecloud}} organization level](/deploy-manage/users-roles/cloud-organization.md). | |
There was a problem hiding this comment.
I like this, but I wonder if we're messing with ourselves a little because we don't have "auth using different mechanisms" as a listing here which possibly sends a less than ideal message
we are using auth realms as a shorthand for SAML / platform-managed / other types of SSO
wonder if it would make more sense to change the feature name to something else and then be even more precise in the fields.
self-managed gets "available (authentication realms)", ech gets "available (auth realms + ecloud sso" and serverless gets "ecloud sso only" (or maybe ece gets unique treatment due to their limited sso capabilities)
or something. lmk if you think
| | [Security configurations](/deploy-manage/security.md) | Full control | Limited control | Limited control | | ||
| | [Authentication realms](/deploy-manage/users-roles.md) | Available | Available | Available, through {{ecloud}} only | | ||
| | [Custom roles](/deploy-manage/users-roles.md) | Available | Available | Available | | ||
| | [Authentication](/deploy-manage/users-roles.md) | {{es}} realms | {{es}} realms, {{ecloud}} SSO | {{ecloud}} SSO only | |
There was a problem hiding this comment.
@shainaraskas : let me know your thoughts on that new line. I've tried to keep it simple. I think removing the word realm is better if we were not really referring specifically about {{es}} auth realms and it was more about authentication in general.
I've also paired ECE with ECH here as they are similar (they support ES realms + cloud SSO).
One comment about "Security configuration" (maybe for a different PR). I'd prefer to say in ECE and ECK "limited control", as some areas are hanlded by the orchestrators like the TLS certs for transport, etc. That's also another plus to have moved ECE to stay together with ECH more than with "fully self-managed".
There was a problem hiding this comment.
copy lgtm
One comment about "Security configuration" (maybe for a different PR). I'd prefer to say in ECE and ECK "limited control", as some areas are hanlded by the orchestrators like the TLS certs for transport, etc. That's also another plus to have moved ECE to stay together with ECH more than with "fully self-managed".
👍
| | [Security configurations](/deploy-manage/security.md) | Full control | Limited control | Limited control | | ||
| | [Authentication realms](/deploy-manage/users-roles.md) | Available | Available | Available, through {{ecloud}} only | | ||
| | [Custom roles](/deploy-manage/users-roles.md) | Available | Available | Available | | ||
| | [Authentication](/deploy-manage/users-roles.md) | {{es}} realms | {{es}} realms, {{ecloud}} SSO | {{ecloud}} SSO only | |
There was a problem hiding this comment.
copy lgtm
One comment about "Security configuration" (maybe for a different PR). I'd prefer to say in ECE and ECK "limited control", as some areas are hanlded by the orchestrators like the TLS certs for transport, etc. That's also another plus to have moved ECE to stay together with ECH more than with "fully self-managed".
👍
Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com>
3 participants
An attempt to solve https://github.com/elastic/docs-content-internal/issues/384
Closes https://github.com/elastic/docs-content-internal/issues/384