Il 20/05/19 20:23, Misagh Moayyed ha scritto:
This might get you started in the right direction:
https://apereo.github.io/2019/05/13/cas61x-mfa-selection-strategies/
Hi Misagh, thank you for this input.
Just a pair of questions more:
* How do I have to configure ranking in case of custom
Hello guys,
I'm still trying to configure a groovy script for access strategy but I
have some errors
Here's my access-strategy.groovy
import org.apereo.cas.services.*
import java.util.*
class GroovyRegisteredAccessStrategy extends
DefaultRegisteredServiceAccessStrategy {
@Override
Hi,
I'm trying to set up a new CAS implementation that delegates to multiple
SAML IdPs, with each IdP representing a distinct slice of the user base
(one IdP per customer).
Is there a way for me to restrict one IdP from attempting to authenticate a
user from another IdP?
I thought about
Hi Alberto,
See if the below info helps you:
- depends on your CAS version, you might need to use
cas.standalone.configurationDirectory=/etc/cas/config
instead of cas.standalone.config=/etc/cas/config
- bootstrap.properties load before application.properties or
application.yml, that's why your
* CAS SSO do not work without https
On Tuesday, 21 May 2019 20:36:33 UTC+8, Andy Ng wrote:
>
> Dear Lee,
>
> Seeing your log, I suspect you are using http instead of https for your
> CAS server,
>
> CAS SSO do not work with https, if you are not using https, please
> configure CAS to use https
Dear Lee,
Seeing your log, I suspect you are using http instead of https for your CAS
server,
CAS SSO do not work with https, if you are not using https, please
configure CAS to use https
Cheers!
- Andy
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom:
Hi all,
I got a similar issue when I try to verify the jwt signature with several
libreries including Node.js jsonwebtoken, since the library allows only
base64url encoded tokens because of mentioned RFC7515.
With java-jwt library the token is correctly verified.
Debugging the code i found in
Debian,
In doPrincipal..., you are using a variable called 'map' but the variable is
'attributes'.
Ray
On Tue, 2019-05-21 at 02:22 -0700, Debian HNT wrote:
Hello guys,
I'm still trying to configure a groovy script for access strategy but I have
some errors
Here's my access-strategy.groovy
Hey Ray,
We want to delegate authentication from CAS to these client IdPs. We'll
either use an IdP-initiated flow, or we'll build out an "SP-initiated flow"
in CAS. Something like this,
1) User hits protected service and is redirected to CAS
2) "Magic IdP resolution" (TBD) forwards them to
Va,
'usage' in mvnrepository means how many projects have a dependency on that
project, not number of downloads.
Ray
On Sun, 2019-05-19 at 07:28 -0700, Va Sja wrote:
Hmm...
..looks really like "Security through obscurity" :((
Guys - how many peoples use CAS worldwide?
looks like nobody?
SRC:
Brent,
Are you saying that the user authenticates first with CAS and is then
redirected to a SAML IdP? Or how will you determine to which IdP a user will be
sent?
Ray
On Tue, 2019-05-21 at 07:45 -0700, Brent Smith wrote:
Hi,
I'm trying to set up a new CAS implementation that delegates to
Brent,
Steps 3) and 4) are confusing. If IdP is performing authentication in 3), why
is CAS also validating credentials?
Picking from a list (or typing it in) is frequently used as a method for IdP
selection. User name would also work but may be a little confusing to users
when they enter the
12 matches
Mail list logo
