[doc] Use name Authentic 2
This commit is contained in:
parent
72ec4a3099
commit
40c36926e5
|
@ -1,8 +1,8 @@
|
|||
.. _administration_with_policies:
|
||||
|
||||
=========================================================
|
||||
==========================================================
|
||||
How global policies are used in Authentic 2 administration
|
||||
=========================================================
|
||||
==========================================================
|
||||
|
||||
The policy management with global policies is nearly used for any kind of
|
||||
policy in Authentic 2.
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
.. _attribute_management:
|
||||
|
||||
==================================
|
||||
===================================
|
||||
Attribute Management in Authentic 2
|
||||
==================================
|
||||
===================================
|
||||
|
||||
Summary
|
||||
=======
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
.. _auth_pam:
|
||||
|
||||
=====================================
|
||||
======================================
|
||||
Authentication on Authentic 2 with PAM
|
||||
=====================================
|
||||
======================================
|
||||
|
||||
This module is copied from https://bitbucket.org/wnielson/django-pam/ by Weston
|
||||
Nielson and the pam ctype module by Chris Atlee http://atlee.ca/software/pam/.
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
.. _config_cas_idp:
|
||||
|
||||
====================================
|
||||
=====================================
|
||||
Configure Authentic 2 as a CAS client
|
||||
====================================
|
||||
=====================================
|
||||
|
|
|
@ -1,11 +1,11 @@
|
|||
.. _config_cas_sp:
|
||||
|
||||
====================================
|
||||
=====================================
|
||||
Configure Authentic 2 as a CAS server
|
||||
====================================
|
||||
=====================================
|
||||
|
||||
How to use Authentic 2 as a CAS 1.0 or CAS 2.0 identity provider ?
|
||||
-----------------------------------------------------------------
|
||||
------------------------------------------------------------------
|
||||
|
||||
1. Activate CAS IdP support in settings.py::
|
||||
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
.. _config_saml2_idp:
|
||||
|
||||
=================================================================
|
||||
==================================================================
|
||||
Configure Authentic 2 as a SAML2 service provider or a SAML2 proxy
|
||||
=================================================================
|
||||
==================================================================
|
||||
|
||||
**The configuration to make Authentic 2 a SAML2 service provider or a SAML2
|
||||
proxy is the same. The difference comes from that Authentic 2 is may be
|
||||
|
@ -18,7 +18,7 @@ Go to http[s]://your.domain.com/authsaml2/metadata
|
|||
2. Add and configure a SAML2 identity provider entry in Authentic 2 using the metadata of the identity provider.
|
||||
|
||||
How do I add and configure a SAML2 identity provider in Authentic 2?
|
||||
===================================================================
|
||||
====================================================================
|
||||
|
||||
You first need to create a SAML2 identity provider entry with the SAML2
|
||||
metadata of the identity provider. Then, you configure it.
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
.. _consent_management:
|
||||
|
||||
================================
|
||||
=================================
|
||||
Consent Management in Authentic 2
|
||||
================================
|
||||
=================================
|
||||
|
||||
What is the SAML2 federation consent aka account linking consent?
|
||||
=================================================================
|
||||
|
|
|
@ -3,9 +3,9 @@
|
|||
You can adapt this file completely to your liking, but it should at least
|
||||
contain the root `toctree` directive.
|
||||
|
||||
==========================
|
||||
===========================
|
||||
Authentic 2's documentation
|
||||
==========================
|
||||
===========================
|
||||
|
||||
Authentic 2 is a versatile identity provider addressing a broad
|
||||
range of needs, from simple to advanced setups, around web authentication,
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
.. _saml2_slo:
|
||||
|
||||
======================================
|
||||
=======================================
|
||||
Single Logout Management in Authentic 2
|
||||
======================================
|
||||
=======================================
|
||||
|
||||
Explanation
|
||||
===========
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
.. _where_metadata:
|
||||
|
||||
==============================================
|
||||
===============================================
|
||||
Where do I find the Authentic 2 SAML2 metadata?
|
||||
==============================================
|
||||
===============================================
|
||||
|
||||
The SAML2 metadata are automatically generated.
|
||||
|
||||
|
|
Reference in New Issue