You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 19, 2022. It is now read-only.
Filter is intended to extract an attribute specified by set of keys forming the chain of keys in the `$request` variable into the configured destination attribute.
167
+
168
+
Configuration options:
169
+
*`attr_name`: specifies attribute name, into which the extracted value will be stored
170
+
*`request_keys`: string, which contains a semicolon (`;`) separated chain of keys that are examined in the state. Numeric keys are automatically treated as array indexes. For instance, value `'saml:AuthenticatingAuthority;0'` will be treated as code `$request['saml:AuthenticatingAuthority'][0]`. In case of this value being empty, exception is thrown. Otherwise, extracted value is stored into the configured destination attribute.
171
+
*`fail_on_nonexisting_keys`: `true` or `false`, specifies if in case of missing key in the request variable the filter should terminate with an exception or not
172
+
*`default_value`: array, which will be set as default value, if the configured keys did not lead to value
173
+
174
+
```php
175
+
// EXTRACT AUTHENTICATING ENTITY INTO authenticating_idp attribute
Filter tries to identify the Perun user. It uses the combination of user identifier and IdP identifier to find the user (or to be more precise, the user identity and associated user account). If it can, the user object is set to `$request` parameter into `$request[PerunConstants::PERUN][PerunConstants::USER]`. Otherwise, user is forwarded to configured registration.
188
+
189
+
Configuration options:
190
+
*`interface`: specifies what interface of Perun should be used to fetch data. See class `SimpleSAML\Module\perun\PerunAdapter` for more details.
191
+
*`uid_attrs`: list of attributes that contain user identifiers to be used for identification. The order of the items in the list represents the priority.
192
+
*`idp_id_attr`: name of the attribute (from `$request['Attributes']` array), which holds EntityID of the identity provider that has performed the authentication.
193
+
*`register_url`: URL to which the user will be forwarded for registration. Leave empty to use the Perun registrar.
194
+
*`callback_parameter_name`: name of the parameter wich will hold callback URL, where the user should be redirected after the registration on URL configured in the `register_url` property.
195
+
*`perun_register_url`: the complete URL (including vo and group) to which user will be redirected, if `register_url` has not been configured. Parameters targetnew, targetexisting and targetextended will be set to callback URL to continue after the registration is completed.
Filter fetches the given attribute holding approved AUP and checks, if expected value is set in the attribute or not. If not, it redirects the user to specified registration component, where user will be asked to approve the AUP.
212
+
213
+
Configuration options:
214
+
*`interface`: specifies what interface of Perun should be used to fetch data. See class `SimpleSAML\Module\perun\PerunAdapter` for more details.
215
+
*`attribute`: name of the attribute, which will be fetched from Perun and holds the value of approved AUP.
216
+
*`value`: value that is expected in the attribute as mark of approved AUP. Expected is a string.
217
+
*`approval_url`: URL to which the user will be forwarded for registration. Leave empty to use the Perun registrar.
218
+
*`callback_parameter_name`: name of the parameter wich will hold callback URL, where the user should be redirected after the AUP approval on URL configured in the `approval_url` property.
219
+
*`perun_register_url`: the complete URL (including vo and group) to which user will be redirected, if `approval_url` has not been configured. Parameters targetnew, targetexisting and targetextended will be set to callback URL to continue after the AUP approval is completed.
Adds qualifiers into NameID based on the configuration
250
+
251
+
Configuration options:
252
+
*`name_id_attribute`: Attribute (NameID) which should be qualified
253
+
*`name_qualifier_attribute`: User attribute with value, which will be set as the NameQualifier part of the NameID. Leave empty to use static value configured via option `name_qualifier`.
254
+
*`name_qualifier`: Static value which will be set as the NameQualifier part of the NameID.
255
+
*`sp_name_qualifier_attribute`: User attribute with value, which will be set as the SPNameQualifier part of the NameID. Leave empty to use static value configured via option `sp_name_qualifier`.
256
+
*`sp_name_qualifier`: Static value which will be set as the SPNameQualifier part of the NameID.
Gets metadata of the IdP specified by `idp_identifier_attribute` value and tries to set the specified keys from IdP metadata into attributes.
272
+
273
+
Configuration options:
274
+
*`idp_identifier_attribute`: Attribute holding the identifier of the Authenticating IdP
275
+
*`attribute_map`: Map of IdP metadata attributes, where keys are the colon separated keys that will be searched in IdP metadata and values are the destination attribute names.
Performs authorization check define dby the SP based on group membership in Perun. User has to be valid member of at least one of the groups assigned to resources of the facility representing the service. If not satisfied, the filter check if registration is enabled. In case of enabled registration, user is forwarded to custom registration link (if configured), or to a dynamic form, where user will select the combination of VO and group to which he/she applies for access. Form then forwards user to Perun registration component. In all other cases, user is forwarded to access denied page.
291
+
NOTE: for correct functionality, RPC adapter must be available, as other adapters cannot fetch info about what groups allow registration (have registration forms) and similar data.
292
+
293
+
Configuration options:
294
+
*`interface`: specifies what interface of Perun should be used to fetch data. See class `SimpleSAML\Module\perun\PerunAdapter` for more details.
295
+
*`registrar_url`: URL where Perun registration component is located. Expected URL is the base, without any parameters.
296
+
*`check_group_membership_attr`: mapping to the attribute containing flag, if membership check should be performed.
297
+
*`vo_short_names_attr`: mapping to the attribute containing shortnames of the VOs for which the service has resources (gives access to the groups).
298
+
*`registration_link_attr`: mapping to the attribute containing custom service registration link. Filter adds the callback URL, to which to redirect user after the registration, as query string in form of 'callback=URL'.
299
+
*`allow_registration_attr`: mapping to the attribute containing flag, if registration in case of denied access is enabled
Copy file name to clipboardExpand all lines: dictionaries/perun.definition.json
+61Lines changed: 61 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -94,5 +94,66 @@
94
94
"unauthorized-access_redirect_to_registration": {
95
95
"en": "Now you will be redirected to registration to Perun system.",
96
96
"cs": "Nyní budete přesměrování na registraci do systému Perun."
97
+
},
98
+
"register_text": {
99
+
"en": "Oops! It seems you have tried to access service via Perun AAI, but yo do not have an account. Let's fix that!",
100
+
"cs": "Ups! Zdá se, že jste se pokusil(a) přihlásit ke službě skrz Perun AAI, no nemáte uživatelský účet. Pojďme to napravit!"
101
+
},
102
+
"register_button": {
103
+
"en": "Proceed to register for an account",
104
+
"cs": "Pokračovat na registraci ůčtu"
105
+
},
106
+
"aup_text": {
107
+
"en": "Oops! It seems you have tried to access service via Perun AAI, but you have not approved the Acceptable Use Policy (AUP). Let's fix that!",
108
+
"cs": "Ups! Vyzerá to, že jste se pokousil(a) přihlásit ke službě skrze Perun AAI, no neschválili jste Podmínky užití služby (AUP). Pojďme to napravit!"
109
+
},
110
+
"aup_button": {
111
+
"en": "Proceed to approval of the AUP",
112
+
"cs": "Pokračovat na potvrzení souhlasu s AUP"
113
+
},
114
+
,
115
+
"sp_authorize_403_header": {
116
+
"en": "Unauthorized",
117
+
"cs": "Přístup zamítnut"
118
+
},
119
+
"sp_authorize_403_text": {
120
+
"en": "You are not authorized to access the service ",
121
+
"cs": "Nesplňujete autorizační pravidla pro přístup ke službě "
122
+
},
123
+
"sp_authorize_403_information_page": {
124
+
"en": "For more information about the service, visit ",
125
+
"cs": "Pro více informací o službě, navštivte "
126
+
},
127
+
"sp_authorize_403_information_page_link_text": {
128
+
"en": "this page",
129
+
"cs": "tuhle stránku"
130
+
},
131
+
"sp_authorize_403_contact_support": {
132
+
"en": "If you think you should have access to the service, please contact the service administrator at ",
133
+
"cs": "Jestli máte mít přístup ke službě, kontaktujte správce služby na "
134
+
},
135
+
"sp_authorize_403_subject": {
136
+
"en": "Unauthorized access",
137
+
"cs": "Přístup zamítnut"
138
+
},
139
+
"sp_authorize_notify_text": {
140
+
"en": "You are not authorized to access the service ",
141
+
"cs": "Nesplňujete autorizační pravidla pro přístup ke službě"
142
+
},
143
+
"sp_authorize_notify_information_page": {
144
+
"en": "For more information about the service, visit ",
0 commit comments