- 06 Dec, 2013 2 commits
-
-
Dionysis Grigoropoulos authored
-
Dionysis Grigoropoulos authored
-
- 05 Dec, 2013 20 commits
-
-
Constantinos Venetsanopoulos authored
Also rename it to "pithos-separate-view domain.rst"
-
Christos Stavrakakis authored
-
Sofia Papagiannaki authored
Change PITHOS_SERVE_API_DOMAIN to PITHOS_UNSAFE_DOMAIN
-
Sofia Papagiannaki authored
The call should return a string value for the user role id.
-
Giorgos Korfiatis authored
-
Sofia Papagiannaki authored
-
Constantinos Venetsanopoulos authored
-
Sofia Papagiannaki authored
-
Giorgos Korfiatis authored
-
Christos Stavrakakis authored
-
Christos Stavrakakis authored
-
Christos Stavrakakis authored
-
Christos Stavrakakis authored
-
Kostas Papadimitriou authored
- Section numbering fix - Include shibboleth upgrade notes
-
Kostas Papadimitriou authored
-
Kostas Papadimitriou authored
include details on how astakos resolve shibboleth unique identifier.
-
Kostas Papadimitriou authored
-
Kostas Papadimitriou authored
Prior to this commit astakos used the mod_shib2 EPPN header value as the unique identifier for associating shibboleth idp users to astakos user entries. This commit alters this behaviour and from now on astakos resloves unique identifier from the REMOTE_USER header. REMOTE_USER is a header mod_shib2 sets containing a value of the available shibboleth IdP metadata. The metadata key (persistent-id or eppn in most common scenarios) used can be configured from within shibboleth2.xml config file. <ApplicationDefaults id="default" .... .... REMOTE_USER="persistent-id"...> An additional setting ``ASTAKOS_SHIBBOLETH_MIGRATE_EPPN`` is added in order to facilitate migration of existing EPPN entries to persistent-id/targeted-id (or whichever metadata the REMOTE_USER maps to). When set to ``True``, after each shibboleth login astakos will try to migrate the existing EPPN entry by following the below mentioned steps: * If no REMOTE_USER header exists or is empty, redirect to an error view. Otherwise continue to the next step. * Resolve EPPN header and check if an account is currently associated with this EPPN. * If user exists, retrieve user's shibboleth entry (AstakosUserAuthProvider instance) and replace stored identifier (EPPN) with the identifier contained in REMOTE_USER header. * Continue to login or signup process using REMOTE_USER value as the unique user identifier that associates astakos user to the shibboleth account. Conflicts: snf-astakos-app/astakos/im/messages.py snf-astakos-app/astakos/im/tests/auth.py
-
Kostas Papadimitriou authored
prefill third party signup form with initial values (first name, last name, email) if available in the third party provider response. Conflicts: snf-astakos-app/astakos/im/views/target/shibboleth.py
-
Ilias Tsitsimpis authored
A new endpoint (astakos_oauth2) was added to Astakos service. Add this endpoint to the astakosclient tests.
-
- 04 Dec, 2013 12 commits
-
-
Christos Stavrakakis authored
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-
Christos Stavrakakis authored
-
Christos Stavrakakis authored
-
Christos Stavrakakis authored
Do not have a default value from 'link' attribute of IP_LESS_ROUTED networks. Instead if the admin does not specify a value in network-create command, uniquely name the networks by with the BACKEND_PREFIX_ID and network id, e.g. snf-link-42.
-
Christos Stavrakakis authored
-
Christos Stavrakakis authored
-
Kostas Papadimitriou authored
-
- 03 Dec, 2013 6 commits
-
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
Delete related authorization codes and tokens before deleting the client
-
Sofia Papagiannaki authored
-
Sofia Papagiannaki authored
-