Skip to content
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

Replace final-redirect-url with juju-dashboard-location #46

Merged
merged 2 commits into from
May 30, 2024
Merged

Replace final-redirect-url with juju-dashboard-location #46

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3cd7c7d
Replace `final-redirect-url` with `juju-dashboard-location`
babakks May 29, 2024
a429459
Explain setting `juju-dashboard-url` to any URL
babakks May 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions tutorial/deploy_jimm_microk8s.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,8 +237,19 @@ Run the following commands:
# A private and public key for macaroon based authentication with Juju controllers.
juju config jimm public-key="<public-key>"
juju config jimm private-key="<private-key>"
# A final redirect URL for login, normally set to the URL of the Juju dashboard.
juju config jimm final-redirect-url="http://test-jimm.localhost/auth/whoami"

Optionally, if you have deployed Juju Dashboard, you can configure JIMM to enable browser flow for authentication:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's tweak this slightly for the purposes of the tutorial so that the dashboard location is still configured so that the user can still test the browser flow. What do you think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, sure. I'll set it with the same /auth/whoami we had, but will point out that this should be replaced with dashboard URL.


.. code:: bash

juju config jimm juju-dashboard-location="<juju-dashboard-url>"

.. note::
However, in absence of a Juju Dashboard, you can still enable OAuth browser authentication flow by setting this parameter to any valid URL. For example:

.. code:: bash

juju config jimm juju-dashboard-location="http://test-jimm.localhost/auth/whoami"

Note that the public and private key pairs must be generated by the `go macaroon bakery repository <https://github.com/go-macaroon-bakery/macaroon-bakery>`__.
To do this briefly run the following command, ensuring you have the ``go`` tool installed:
Expand Down
Loading