8000 docs: update intro and remove xml edition requirement by jgomer2001 · Pull Request #8331 · JanssenProject/jans · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docs: update intro and remove xml edition requirement #8331

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

Merged
merged 3 commits into from
Apr 18, 2024
Merged

docs: update intro and remove xml edition requirement #8331

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
529e1ca
docs: update intro and remove xml edition requirement #8330
jgomer2001 Apr 17, 2024
4c67c64
Merge branch 'main' into agama-issue_8330
jgomer2001 Apr 17, 2024
5becc2c
Merge branch 'main' into agama-issue_8330
moabu Apr 18, 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
3 changes: 1 addition & 2 deletions docs/agama-catalog/jans/inboundID/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Inbound identity with Agama

Using Agama administrators can delegate authorization to external services like social sites. In a typical setting users are shown a login form with a "Sign in with..." button for authentication to take place at a given 3rd party in order to get access to a target application.
Using Agama administrators can delegate authorization to external services like social sites and enterprise access management solutions, e.g. Microsoft Entra ID, Oracle Access Management, etc. In a typical setting users are presented a login form with a "Sign in with..." button for authentication to take place at a given 3rd party in order to get access to a target application.

This process is usually referred to as "inbound identity". In this document the steps required to setup inbound identity in your Janssen server are presented.

Expand Down Expand Up @@ -65,7 +65,6 @@ Let's add the required libraries to the authentication server:

- Visit [this](https://maven.jans.io/maven/io/jans/agama-inbound/) page, navigate to the folder matching your Janssen server version, and download the jar file
- SSH to the server. Transfer the file to directory `/opt/jans/jetty/jans-auth/custom/libs`
- Navigate to `/opt/jans/jetty/jans-auth/webapps` and edit the file `jans-auth.xml` by adding `<Set name="extraClasspath">./custom/libs/*</Set>` before the root tag closes
- Restart the server, e.g. `systemctl restart jans-auth`

### Make a `gama` archive
Expand Down
0