MojoX-Authentication
view release on metacpan or search on metacpan
lib/MojoX/Authentication/Model/SAML2.pod view on Meta::CPAN
When a request is received past this time-to-live, it is considered
expired.
=head2 B<< sig_hash >>
my $string = $provider->sig_hash;
Accessor for the string holding the signature hashing function to be
used. Defaults to C<undef>, which means that none will be set in
L</idp_login>.
=head2 B<< sp_configuration >>
my $cfg = $provider->sp_configuration;
Accessor for the Service Provider configuration (hash reference). It is
supposed to contain the following keys:
=over
=item *
C<identifier>: the value set as the C<issuer> in L</idp_login>.
=item *
C<key>: the private key of the Service Provider, used to sign the
redirect. It's the path to a file.
=item *
C<sso-post-url-override>: the URL to pass as parameter C<assertion_url>
when building the request in L</idp_login>.
=back
=head2 B<< user_key >>
my $key = $provider->user_key;
Accessor to the key that is set in the user's data with the user
identifier.
=head2 B<< user_ttl >>
my $secs = $provider->user_ttl;
The time-to-live of the cached user when it is correctly parsed. After
this, there will be the need to perform a new interaction with the
Identity Provider.
=head2 B<< username_validator >>
my $sub = $provider->username_validator;
Accessor for the username validation function. This is wrapped by
L</handles_username> behind the scenes, so it should be set to some
validation mechanism that allows figuring out if the specific SAML2
Identity Provider is the right one for the username.
=head2 B<< validate_user >>
my $uid = $provider->validate_user($ctr, $user, $secret, $extra);
Do the user validation, compatibly with
L<Mojolicious::Plugin::Authentication>.
=head2 B<< wipe_user >>
$provider->wipe_user($user);
Remove the user from the cache.
=head1 ANYTHING ELSE (INCLUDING AUTHOR, COPYRIGHT AND LICENSE)
See documentation for L<MojoX::Authentication>.
=cut
( run in 0.812 second using v1.01-cache-2.11-cpan-0b5f733616e )