Skip to content

Commit

Permalink
Updates to documentation
Browse files Browse the repository at this point in the history
- Remove mentions of Candid
- Remove old defunc docs
  • Loading branch information
kian99 committed Jun 13, 2024
1 parent 49ab28c commit 9a160ef
Show file tree
Hide file tree
Showing 12 changed files with 28 additions and 850 deletions.
2 changes: 0 additions & 2 deletions .custom_wordlist.txt
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,6 @@ APIs
auditability
aws
balancer
Candid
Candid's
certbot
Charmhub
CLI
Expand Down
6 changes: 3 additions & 3 deletions explanation/jaas_security_scope.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ additionally acting as the IdP (Identity Provider) for said tokens.
Access control and authentication
---------------------------------
JAAS provides an abstraction layer of access control on top of Juju. JAAS does this by backing its users
with an IdP (Identity Provider), this particular IdP is called Candid which handles the authentication
for JIMM (Juju Intelligent Model Manager, the back-end to JAAS). Furthermore, JAAS is capable of many
authentication and authorisation types, ranging from users to agents. For authorisation, JAAS provides
with an IdP (Identity Provider), many identity providers exist e.g. cloud providers like Google and Microsft can be used
as an IdP. We recommend the `Canonical identity platform <https://charmhub.io/topics/canonical-identity-platform>`__
as the preferred IdP for JAAS. The IdP will handle user authentication on behalf of JAAS. For authorisation, JAAS provides
this by means of tags and ReBAC (Relation Based Access Control).

Auditing and logging
Expand Down
3 changes: 1 addition & 2 deletions explanation/jaas_tags.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,7 @@ A user tag has the following format:
user-<username>
where ``username`` uniquely identifies a user including the domain specified
by Candid.
where ``username`` uniquely identifies a user including the domain.

Group
-----
Expand Down
45 changes: 0 additions & 45 deletions how-to/deploy_jimm.rst

This file was deleted.

259 changes: 0 additions & 259 deletions how-to/deploy_jimm_k8s.rst

This file was deleted.

13 changes: 0 additions & 13 deletions how-to/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,18 +3,6 @@ How-to guides

These how-to guides cover key operations and processes in JAAS.

JIMM Deployment
---------------

Here are instructions on how to deploy JIMM.

.. toctree::
:maxdepth: 1

Deploy JIMM <deploy_jimm>
Deploy JIMM on K8S <deploy_jimm_k8s>


JIMM Configuration
------------------

Expand All @@ -27,7 +15,6 @@ After JIMM has been deployed, you need to configure it with your Juju operated c
Add a controller to JIMM <add_controller>
Migrate models to JAAS <migrate_models>
Migrate models internally <migrate_models_internal>
Set up Route53 <route53>

Terraform
---------
Expand Down
Loading

0 comments on commit 9a160ef

Please sign in to comment.