New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Simplify anonymous access & embedding docs. #90409

Merged

azasypkin merged 11 commits into elastic:master from azasypkin:issue-xxx-simplify-anonymous-docs

Feb 23, 2021

Member

azasypkin commented Feb 5, 2021 •

edited

Loading

Summary

Since #86965 is merged and we now have a more user-friendly approach to anonymously share dashboards, visualizations and saved searches, we shouldn't expose internal implementation details anymore.

Preview: https://kibana_90409.docs-preview.app.elstc.co/guide/en/kibana/master/kibana-authentication.html#anonymous-authentication


          Simply anonymous access & embedding docs.

7edec76

azasypkin added Team:Docs Team:Security Feature:Security/Authentication v8.0.0 docs v7.11.0 v7.12.0 labels

Contributor

elasticmachine commented Feb 5, 2021

Pinging @elastic/kibana-docs (Team:Docs)

Contributor

elasticmachine commented Feb 5, 2021

Pinging @elastic/kibana-security (Team:Security)

azasypkin added the release_note:skip label

legrego reviewed

View reviewed changes

docs/user/security/authentication/index.asciidoc Outdated

    
            @@ -383,21 +383,11 @@ xpack.security.authc.providers:
          
              One of the most popular use cases for anonymous access is when you embed {kib} into other applications and don't want to force your users to log in to view it. If you configured {kib} to use anonymous access as the sole authentication mechanism, you don't need to do anything special while embedding {kib}.

              If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding, then you will need to add the `auth_provider_hint=<anonymous-provider-name>` query string parameter to the {kib} URL that you're embedding.

              If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding dashboards or visualizations, then toggle `Public URL` switch presented in the embedding menu.

Member

legrego Feb 5, 2021

What do you think about including a screenshot of this switch within the embedding menu? That would help users discover the feature if they haven't used/seen the embedding menu before.

Member Author

azasypkin Feb 5, 2021

Yep, was hesitating about that (quickly may become outdated and such), but since you mentioned.... I'll add it.

Member

legrego Feb 5, 2021

Yeah I share your concerns about outdated screenshots. I struggle with the decision every time I write docs, too

Contributor

gchaps Feb 5, 2021

I agree that a screenshot is needed here.

docs/user/security/authentication/index.asciidoc

		@@ -383,21 +383,11 @@ xpack.security.authc.providers:

		One of the most popular use cases for anonymous access is when you embed {kib} into other applications and don't want to force your users to log in to view it. If you configured {kib} to use anonymous access as the sole authentication mechanism, you don't need to do anything special while embedding {kib}.

		If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding, then you will need to add the `auth_provider_hint=<anonymous-provider-name>` query string parameter to the {kib} URL that you're embedding.

This comment was marked as resolved.

Sign in to view

This comment was marked as resolved.

Sign in to view

This comment was marked as resolved.

Sign in to view

This comment was marked as resolved.

Sign in to view

gchaps reviewed

View reviewed changes

docs/user/security/authentication/index.asciidoc Outdated

    
            @@ -383,21 +383,11 @@ xpack.security.authc.providers:
          
              One of the most popular use cases for anonymous access is when you embed {kib} into other applications and don't want to force your users to log in to view it. If you configured {kib} to use anonymous access as the sole authentication mechanism, you don't need to do anything special while embedding {kib}.

              If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding, then you will need to add the `auth_provider_hint=<anonymous-provider-name>` query string parameter to the {kib} URL that you're embedding.

              If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding dashboards or visualizations, then toggle `Public URL` switch presented in the embedding menu.

Contributor

gchaps Feb 5, 2021

I agree that a screenshot is needed here.

docs/user/security/authentication/index.asciidoc Outdated

    
            @@ -383,21 +383,11 @@ xpack.security.authc.providers:
          
              One of the most popular use cases for anonymous access is when you embed {kib} into other applications and don't want to force your users to log in to view it. If you configured {kib} to use anonymous access as the sole authentication mechanism, you don't need to do anything special while embedding {kib}.

              If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding, then you will need to add the `auth_provider_hint=<anonymous-provider-name>` query string parameter to the {kib} URL that you're embedding.

              If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding dashboards or visualizations, then toggle `Public URL` switch presented in the embedding menu.

Contributor

gchaps Feb 5, 2021

Can we mention the saved objects it applies to and which apps the menu item is available from?

Suggested change

      
            If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding dashboards or visualizations, then toggle `Public URL` switch presented in the embedding menu.
          
            If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding dashboards, visualizations, and saved searches, then toggle *Public URL* in the *Share > Embed code* menu in  *Dashboard*, *Visualize*, or *Discover*.

Member Author

azasypkin Feb 8, 2021

If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding dashboards, visualizations, and saved searches, then toggle Public URL in the Share > Embed code menu in Dashboard, Visualize, or Discover.

Thanks, but will omit saved searches and Discover since we don't support embedding for them.

Contributor

gchaps Feb 8, 2021

++

docs/user/security/authentication/index.asciidoc Outdated


		For example, if you generate the iframe code to embed {kib}, it will look like this:
		You can also use `Public URL` switch when you're generating permanent links to dashboards, visualizations or saved searches.

Contributor

gchaps Feb 5, 2021

Suggested change

      
            You can also use `Public URL` switch when you're generating permanent links to dashboards, visualizations or saved searches.
          
            You can also use the *Public URL* toggle when you're generating permanent links to dashboards, visualizations, and saved searches.

docs/user/security/authentication/index.asciidoc Outdated

-              ```
-              Note that `auth_provider_hint` query string parameter goes *before* the hash URL fragment.
+              NOTE: `Public URL` switch is only available if anonymous access is properly configured and anonymous service account has enough privileges to access what you want to embed or share.

Contributor

gchaps Feb 5, 2021

Suggested change

      
            NOTE: `Public URL` switch is only available if anonymous access is properly configured and anonymous service account has enough privileges to access what you want to embed or share.
          
            NOTE:  The *Public URL* toggle is only available if anonymous access is properly configured and your anonymous service account has privileges to access what you want to embed or share.

azasypkin added 3 commits

February 15, 2021 14:54


          Merge branch 'master' into issue-xxx-simplify-anonymous-docs

67d1119


          Merge branch 'master' into issue-xxx-simplify-anonymous-docs

26a456d


          Review#1: handle review feedback and add dedicated section for embedd…

e2ed50b

…ing.

jportner self-requested a review

February 16, 2021 15:16

gchaps reviewed

View reviewed changes

docs/setup/embedding.asciidoc Outdated

+              [[embedding]]
+              == Embedding {kib}
+              You can embed a {kib} dashboard or visualization using an HTML code snippet generated with the *Copy iFrame code* button in *Share > Embed code* menu in *Dashboard* or *Visualize*.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated


		NOTE: Embedding of any other part of {kib} is also generally possible, but you may need to craft the proper HTML code manually.

		[role="screenshot"]

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              [[embedding-security]]
+              === Configure security
+              Embedding through iframes, if used properly, does not directly pose a security risk, but still requires a careful consideration.

Contributor

gchaps Feb 16, 2021

Is it worth explaining what some of these considerations are?

Contributor

jportner Feb 17, 2021 •

edited

Loading

I'll chime in here -- I think we should reword this. Nothing is zero-risk, and this statement could be misinterpreted. How about this?

Suggested change

      
            Embedding through iframes, if used properly, does not directly pose a security risk, but still requires a careful consideration.
          
            Embedding content through iframes requires careful consideration to minimize security risks. By default, modern web browsers enforce the
          
            https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy[same-origin policy] to restrict the behavior of framed pages. When
          
            {stack-security-features} are enabled on your cluster, you must relax this constraint for cookies as described below for {kib} to function
          
            in an iframe. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe[iframe] and
          
            https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite[SameSite cookies] documentation for more information.

Note that we have a few links to MDN docs here, which there is precedent for in some other docs.

Member Author

azasypkin Feb 19, 2021

Note that we have a few links to MDN docs here, which there is precedent for in some other docs.

MDN is the well-known and trusted source of such information, I assume it should be fine. @gchaps do you have any concerns?

docs/setup/embedding.asciidoc Outdated

+              [float]
+              ==== Authentication
+              If you're embedding {kib} to the website that supports Single Sign-On with SAML, OpenID Connect, Kerberos or PKI it's highly advisable to configure {kib} as a part of this Single Sign-On setup as well. Operating within a single and properly configured security domain would provide you with the most secure and seamless user experience. You can read more at <<kibana-authentication, Authentication in {kib}>>.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              ==== Authentication
+              If you're embedding {kib} to the website that supports Single Sign-On with SAML, OpenID Connect, Kerberos or PKI it's highly advisable to configure {kib} as a part of this Single Sign-On setup as well. Operating within a single and properly configured security domain would provide you with the most secure and seamless user experience. You can read more at <<kibana-authentication, Authentication in {kib}>>.
+              If you want anyone to access embedded {kib} skipping the login step, but the Single Sign-On isn't an option for you, consider configuring the <<anonymous-authentication, anonymous access>> instead. It is already natively integrated into the embedding workflow for the dashboards and visualizations.

This comment was marked as resolved.

Sign in to view

This comment was marked as resolved.

Sign in to view

This comment was marked as resolved.

Sign in to view

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated


		If you have multiple authentication providers enabled, and you want to automatically log in anonymous users when embedding anything other than dashboards and visualizations, then you will need to add the `auth_provider_hint=<anonymous-provider-name>` query string parameter to the {kib} URL that you're embedding.

		For example, if you craft the iframe code to embed {kib}, it may look like this:

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              <iframe src="https://localhost:5601/app/monitoring?auth_provider_hint=anonymous1#/elasticsearch/nodes?embed=true&_g=(....)" height="600" width="800"></iframe>
+              ```
+              Note that `auth_provider_hint` query string parameter goes *before* the hash URL fragment.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              [float]
+              ==== Cookies
+              Irrespective to the authentication type you're going to use for the embedded {kib} you need to make sure that browsers can transmit session cookies to a {kib} server. The setting you need to be aware of is <<xpack-security-sameSiteCookies, `xpack.security.sameSiteCookies`>>, and to support modern browsers, you might need to set it to `None`:

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              xpack.security.sameSiteCookies: "None"
+              --
+              You can find more information about possible values and implications <<xpack-security-sameSiteCookies, here>>.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              [[embedding]]
+              == Embedding {kib}
+              You can embed a {kib} dashboard or visualization using an HTML code snippet generated with the *Copy iFrame code* button in *Share > Embed code* menu in *Dashboard* or *Visualize*.

Contributor

gchaps Feb 16, 2021

It would be good to provide some information about why you would want to embed a Kibana dashboard or visualization. Can you also embed saved searches?

Member Author

azasypkin Feb 16, 2021

It would be good to provide some information about why you would want to embed a Kibana dashboard or visualization.

Sure, let me think how to phrase that properly.

Can you also embed saved searches?

Technically you can embed anything. You just create an iframe and put any Kibana URL there assuming it works for your use case and you don't mind the risk of breaking it in any release.

I'd say we want to encourage our users to embed only what we officially support and provide advanced sharing controls for. But we also know that some users will still embed Kibana in very surprising ways. These are the users we're targeting in the section with auth_provider_hint.


          Merge branch 'master' into issue-xxx-simplify-anonymous-docs

436322e

azasypkin added the auto-backport label

jportner reviewed

View reviewed changes

Contributor

jportner left a comment •

edited

Loading

I like the content, but I had to read three different pages a few times before I really understood how to do this using the ES anonymous user ("Embedding Kibana", "Authentication in Kibana", "Enabling anonymous access"). The fact that there are several ways to configure anonymous authentication in Kibana (one of which requires ES to have anonymous access enabled too) is a bit overwhelming IMO. High level feedback:

"Authentication in Kibana"

I like this page as-is, it does a great job explaining the different options. This is a good example of "Reference" documentation IMO:

I can't comment on this inline because this part of the page hasn't been changed in this PR, but the only complaint I have is the part in the Anonymous Authentication section where it says "There are three ways to specify these credentials:". It really specifies four ways to configure anonymous authentication. Is there a better way we can organize that? Perhaps split it up with sub-headings with something like this?

Anonymous authentication with a user account
a. With username and password
b. With an API key (base64-encoded id:api_key string)
c. With an API key (id and api_key values)
Anonymous authentication using Elasticsearch anonymous access

"Embedding Kibana"

I like this page, but as I alluded above, I was not able to easily figure out what to do by reading it. In the quad chart above, this reads like "Reference" documentation. I think we really need this page to be more of a "How-to Guide". If a user is coming to this page, they likely want to figure out exactly what to do to embed Kibana in a webpage. I'd prefer if we could outline all the steps to do so:

Create a user account
Create a role for this user account (assign it minimal privileges)
Reconfigure Kibana to add an anonymous auth provider that utilizes this account
Open a dashboard and get the embeddable iframe code

WDYT?

Contributor

gchaps commented Feb 17, 2021

+1 for a how-to guide.

Member Author

azasypkin commented Feb 18, 2021

These are all great ideas @jportner, thanks! I feel that the scope of this PR is significantly drifting away from the initial goal though. The goal was to recommend using Public URL switch instead of manually adding auth_provider_hint query string parameter when anonymous access is enabled and do some groundwork for the embedding docs so that authentication section can reference to it. But it sounds like my "better-some-docs-than-no-docs" plan didn't work out and sparse embedding section just adds more confusion.

I think I'll just stick to the initial plan and completely remove embedding section from this PR to unblock it and try to come up with a how-to guide for embedding in the near future. Does that sound good?

I'd prefer if we could outline all the steps to do so:

Create a user account

Create a role for this user account (assign it minimal privileges)

Reconfigure Kibana to add an anonymous auth provider that utilizes this account

Open a dashboard and get the embeddable iframe code

I believe we want to endorse using SSO for embedding as the easiest (no need to configure anonymous service account separately), the most flexible (different users may see different things) and the safest approach (less risk to give too much privileges to the anonymous service account in attempt to cater the needs of all user groups in a single account). I still see embedding with the anonymous access as the fallback when SSO isn't an option, a necessary evil if you will.

That's why I'd like the How-To guide to start from the praise to SSO approach and only then mention anonymous access with all the steps you suggested. I don't have the full picture of how that guide should look like in my head yet, so I'll make a step back and think a little bit more.

Contributor

jportner commented Feb 18, 2021

I feel that the scope of this PR is significantly drifting away from the initial goal though.

Yeah, sorry about that!

I think I'll just stick to the initial plan and completely remove embedding section from this PR to unblock it and try to come up with a how-to guide for embedding in the near future. Does that sound good?

Honestly I think the embedding page has valuable content and we should keep it until we can reorganize/rewrite it in a How-To Guide style.

That's why I'd like the How-To guide to start from the praise to SSO approach and only then mention anonymous access with all the steps you suggested. I don't have the full picture of how that guide should look like in my head yet, so I'll make a step back and think a little bit more.

You make a good argument! I'd be happy to help write this up, let me know 😄

azasypkin added 2 commits

February 19, 2021 10:08


          Merge branch 'master' into issue-xxx-simplify-anonymous-docs

6a9d213


          Review#2: handle review feedback.

60d7ca0

Member Author

azasypkin commented Feb 19, 2021

Honestly I think the embedding page has valuable content and we should keep it until we can reorganize/rewrite it in a How-To Guide style.

Good, I'll keep it here then.

You make a good argument! I'd be happy to help write this up, let me know smile

Thanks! I'll create a draft PR once we are done with this one.

gchaps reviewed

View reviewed changes

docs/setup/embedding.asciidoc Outdated


		Once you create a dashboard, or a visualization you surely might want to share it with your colleagues or friends at some point. The easiest way to do that is to share a direct link to your dashboard or visualization, but not everyone might have access to your {kib} or even know what {kib} is. Moreover, sometimes you might want to give more context to the thing you're sharing, for example, attach analysis, or images, or links, and {kib} isn't always the best tool for this type of job.

		If you have an internal company website or just a personal webpage where it'd make more sense to display the content you created in {kib}, then try out the {kib} embedding functionality. You can embed a {kib} dashboard or visualization using an HTML code snippet generated with the Copy iFrame code button in the Share > Embed code menu in Dashboard or Visualize.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated


		Once you create a dashboard, or a visualization you surely might want to share it with your colleagues or friends at some point. The easiest way to do that is to share a direct link to your dashboard or visualization, but not everyone might have access to your {kib} or even know what {kib} is. Moreover, sometimes you might want to give more context to the thing you're sharing, for example, attach analysis, or images, or links, and {kib} isn't always the best tool for this type of job.

		If you have an internal company website or just a personal webpage where it'd make more sense to display the content you created in {kib}, then try out the {kib} embedding functionality. You can embed a {kib} dashboard or visualization using an HTML code snippet generated with the Copy iFrame code button in the Share > Embed code menu in Dashboard or Visualize.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated


		Once you create a dashboard, or a visualization you surely might want to share it with your colleagues or friends at some point. The easiest way to do that is to share a direct link to your dashboard or visualization, but not everyone might have access to your {kib} or even know what {kib} is. Moreover, sometimes you might want to give more context to the thing you're sharing, for example, attach analysis, or images, or links, and {kib} isn't always the best tool for this type of job.

		If you have an internal company website or just a personal webpage where it'd make more sense to display the content you created in {kib}, then try out the {kib} embedding functionality. You can embed a {kib} dashboard or visualization using an HTML code snippet generated with the Copy iFrame code button in the Share > Embed code menu in Dashboard or Visualize.

Contributor

gchaps Feb 19, 2021

I like the new content! Here is a suggestion that moves things around a bit and removed some of the things that felt a little negative. In the second para, I suggest leading with the Kibana embedding functionality and putting the instructions in the order that that users sees them. Also, the part about adding context felt more natural here.

Once you create a dashboard or a visualization, you might want to share it with your colleagues or friends. The easiest way to do this is to share a direct link to your dashboard or visualization. However, some users might not have access to your {kib}.

With the {kib} embedding functionality, you can display the content you created in {kib} to an internal company website or a personal web page. From Dashboard or Visualize, open the Share > Embed code menu, and then click Copy iFrame code to generate an HTML code snippet. You can embed in this snippet in your web page, and then add analysis, images, and links to give more context to the object you're sharing.

Member Author

azasypkin Feb 22, 2021

Sounds much better, thanks!

docs/setup/embedding.asciidoc Outdated

		@@ -0,0 +1,54 @@
		[[embedding]]
		== Embedding {kib}

Contributor

gchaps Feb 19, 2021

Embedding {kib} content in a web page?

Contributor

wylieconlon Feb 19, 2021

This page looks very useful! Why is it organized as part of setup instead of being part of dashboards?

Member Author

azasypkin Feb 22, 2021

Embedding {kib} content in a web page?

Yeah, sounds good, thanks.

This page looks very useful! Why is it organized as part of setup instead of being part of dashboards?

Basically setup was the only existing top-level section that can potentially cover all parts of Kibana. The idea was to eventually describe everything that can be embedded in one way or another: dashboards, visualizations, canvas, or any random part of Kibana that can technically be embedded (we know people do this).

Contributor

gchaps Feb 22, 2021

We are planning on creating a Share section in the documentation. Would this doc be a good candidate for that?

Member Author

azasypkin Feb 22, 2021

Yes, I think so.

docs/setup/embedding.asciidoc Outdated

+              Embedding content through iframes requires careful consideration to minimize security risks. By default, modern web browsers enforce the
+              https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy[same-origin policy] to restrict the behavior of framed pages. When
+              {stack-security-features} are enabled on your cluster, you must relax this constraint for cookies as described below for {kib} to function

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated


		If you have an internal company website or just a personal webpage where it'd make more sense to display the content you created in {kib}, then try out the {kib} embedding functionality. You can embed a {kib} dashboard or visualization using an HTML code snippet generated with the Copy iFrame code button in the Share > Embed code menu in Dashboard or Visualize.

		NOTE: Embedding of any other part of {kib} is also generally possible, but you may need to craft the proper HTML code manually.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              Embedding content through iframes requires careful consideration to minimize security risks. By default, modern web browsers enforce the
+              https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy[same-origin policy] to restrict the behavior of framed pages. When
+              {stack-security-features} are enabled on your cluster, you must relax this constraint for cookies as described below for {kib} to function
+              in an iframe. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe[iframe] and

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy[same-origin policy] to restrict the behavior of framed pages. When
+              {stack-security-features} are enabled on your cluster, you must relax this constraint for cookies as described below for {kib} to function
+              in an iframe. See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe[iframe] and
+              https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite[SameSite cookies] documentation for more information.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

+              xpack.security.sameSiteCookies: "None"
+              --
+              For more information about possible values and implications, go to <<xpack-security-sameSiteCookies, xpack.security.sameSiteCookies >>.

This comment was marked as resolved.

Sign in to view

azasypkin changed the title ~~Simply anonymous access & embedding docs.~~ Simplify anonymous access & embedding docs.

Contributor

KOTungseth commented Feb 19, 2021

Does this PR cover #18226?

Contributor

jportner commented Feb 19, 2021

Does this PR cover #18226?

@KOTungseth No, but as mentioned in #90409 (comment) we are planning on making a How-To guide that would focus on the SSO (external auth provider) use case. We'll open a new PR and link it to that issue, thanks!

azasypkin added 2 commits

February 22, 2021 12:35


          Merge branch 'master' into issue-xxx-simplify-anonymous-docs

ddf76c7


          Review#3: handle review feedback.

ef5788e

gchaps approved these changes

View reviewed changes

Contributor

gchaps left a comment

LGTM

docs/setup/embedding.asciidoc Outdated


		image::images/embed-kibana.png[Generate an HTML snippet to embed {kib}, align=center]

		NOTE: Embedding of any other part of {kib} is also generally possible, but you may need to craft the proper HTML code manually.

This comment was marked as resolved.

Sign in to view

docs/setup/embedding.asciidoc Outdated

@@ @@ -1,23 +1,23 @@ @@
               [[embedding]]
-              == Embedding {kib}
+              == Embedding {kib} content in a web page

Contributor

gchaps Feb 22, 2021

Suggested change

      
            == Embedding {kib} content in a web page
          
            == Embed {kib} content in a web page

azasypkin requested a review from jportner

February 22, 2021 17:03

jportner approved these changes

View reviewed changes

Contributor

jportner left a comment

🎉

azasypkin added 2 commits

February 23, 2021 08:22


          Merge branch 'master' into issue-xxx-simplify-anonymous-docs

54b2f48


          Review#4: handle review feedaback.

2349a92

azasypkin merged commit 8e2bd8f into elastic:master

azasypkin deleted the issue-xxx-simplify-anonymous-docs branch

February 23, 2021 07:56

Member Author

azasypkin commented Feb 23, 2021

Thanks a lot for review @gchaps @jportner @legrego !

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request


          Simplify anonymous access & embedding docs. (elastic#90409)

019f628

kibanamachine mentioned this pull request

[7.11] Simplify anonymous access & embedding docs. (#90409) #92352

Merged

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request


          Simplify anonymous access & embedding docs. (elastic#90409)

30192e3

kibanamachine mentioned this pull request

[7.12] Simplify anonymous access & embedding docs. (#90409) #92353

Merged

Contributor

kibanamachine commented Feb 23, 2021

💚 Backport successful

✅ 7.11 / #92352
✅ 7.12 / #92353

Successful backport PRs will be merged automatically after passing CI.

kibanamachine added a commit that referenced this pull request


          Simplify anonymous access & embedding docs. (#90409) (#92353)

cb068f6

Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com>

kibanamachine added a commit that referenced this pull request


          Simplify anonymous access & embedding docs. (#90409) (#92352)

f5f9ea5

Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com>

KOTungseth mentioned this pull request

Document how to embed dashboards with external auth provider #18226

Closed

Contributor

jportner commented Mar 10, 2021

It looks like we backported these docs to 7.11, even though the Public URL switch (from the linked PR) is only available in 7.12+ 🙈

I'll push a PR to update the 7.11 docs accordingly.

jportner mentioned this pull request

[7.11] Fix embedding docs #94371

Merged

Member Author

azasypkin commented Mar 11, 2021

Ugh, thanks @jportner for catching this!

azasypkin mentioned this pull request

[7.x] Simplify anonymous access & embedding docs. (#90409) #99747

Merged

azasypkin added the v7.13.0 label

azasypkin mentioned this pull request

[7.13] Simplify anonymous access & embedding docs. (#99747) #99748

Merged

azasypkin added a commit that referenced this pull request


          [7.13] Simplify anonymous access & embedding docs. (#90409)

8c6c652

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport docs Feature:Security/Authentication release_note:skip Team:Docs Team:Security v7.11.0 v7.12.0 v7.13.0 v8.0.0