[cas-user] Build failed (cas-client-integration-atlassian)

[더미]

Hi
Ask for help with build failures.

--

java-cas-client/cas-client-integration-atlassian
mvn clean package
[ERROR] Failed to execute goal on project cas-client-integration-atlassian: 
Could not resolve dependencies for project 
org.jasig.cas.client:cas-client-integration-atlassian:jar:3.6.1: Failed to 
collect dependencies at com.atlassian.seraph:atlassian-seraph:jar:4.0.5: 
Failed to read artifact descriptor for 
com.atlassian.seraph:atlassian-seraph:jar:4.0.5: Failure to find 
com.atlassian.platform:platform:pom:3.1.7 in 
https://maven.atlassian.com/content/repositories/atlassian-public/ was 
cached in the local repository, resolution will not be reattempted until 
the update interval of atlassian has elapsed or updates are forced -> [Help 
1]

--
Thanks

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/99a52681-089d-4376-aec6-6c9ea47c20b7n%40apereo.org.

[cas-user] Ask for help with build failures.

[더미]

Ask for help with build failures.

[ERROR] Failed to execute goal on project cas-client-integration-atlassian: 
Could 
not resolve dependencies for project 
org.jasig.cas.client:cas-client-integration-atlassian:jar:3.6.1: Failed to 
collect dependencies at com.atlassian.seraph:atlassian-seraph:jar:4.0.5: 
Failed to read artifact descriptor for 
com.atlassian.seraph:atlassian-seraph:jar:4.0.5: Failure to find 
com.atlassian.platform:platform:pom:3.1.7 in 
https://maven.atlassian.com/content/repositories/atlassian-public/ was 
cached in the local repository, resolution will not be reattempted until 
the update interval of atlassian has elapsed or updates are forced -> [Help 
1]

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/f59e5c96-4e44-421c-b4c9-4db323731ab3o%40apereo.org.

[cas-user] OAuth password grant fails because UsernamePasswordCredential isn't a ClientCredential

[Gary Rush]

I've gone through several simple example service configurations for both 
6.1.5 and 6.2.0-RC5, and I'm currently trying:

{
  "@class" : "org.apereo.cas.support.oauth.services.OAuthRegisteredService",
  "clientId": "client",
  "clientSecret": "secret",
  "serviceId" : "https://example.net/dashboard;,
  "name" : "OAUTH",
  "id" : 1,
  "attributeReleasePolicy" : {
"@class" : 
"org.apereo.cas.services.ReturnAllowedAttributeReleasePolicy",
"allowedAttributes" : [ "java.util.ArrayList", [ "cn", "mail", "sn" ] ]
  },
  "supportedGrantTypes": [ "java.util.HashSet", [ "password" ] ]
}

When a password grant request is made, CAS cannot find a valid 
authentication handler. A UsernamePasswordCredential is extracted, but the 
DelegatedClientAuthenticationHandler will only accept ClientCredentials. 
Honestly after stepping though the code for days I don't see how this ever 
worked. I assume it does however, so I must be missing something.

curl "[my 
server]/oauth2.0/token?grant_type=password_id=client_secret=secret=user=password"

2020-06-17 15:13:20,269 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.DefaultAuthenticationEventExecutionPlan] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.DefaultAuthenticationEventExecutionPlan] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.DefaultAuthenticationEventExecutionPlan] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.AuthenticationHandlerResolver] - 
2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.DefaultAuthenticationEventExecutionPlan] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 

2020-06-17 15:13:20,270 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 


Any working password grant configuration or insight would be appreciated.

Thanks,
-Gary

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/abd91b30-3194-4f92-9e2b-92277660dc77o%40apereo.org.

Re: [cas-user] SLO within browser context

[Pascal Rigaux]

Hi,

In case you can't use front-channel SLO,
when you use cookie affinity,
here is a solution that duplicates the back-channel SLO request to all  
the backends :

https://github.com/EsupPortail/proxy-broadcast

cu


Paul Roemer  a écrit :


Hey guys,

I just ran into the SLO + loadbalancer issue as some of our CAS clients are
clustered. Now, I wonder if it is possible to send the POST logout requests
to the services participating at the current SSO session from within the
browser/from client side instead of sending them from the CAS server.

If that is possible, I expect the load balancer issue is solved without
further adjustments as it will redirect the request to the correct node in
case of a clustered CAS client.

What are your thougts?

Cheers,
  Paul

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google  
Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it,  
send an email to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit  
https://groups.google.com/a/apereo.org/d/msgid/cas-user/95830dcf-aa6a-44df-8c7e-7d84d517f83an%40apereo.org.




--
Pascal Rigaux

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/20200617182928.Horde.Ly8CnNiQnM6PD1qL2dzmifH%40courrier.univ-paris1.fr.

Re: [cas-user] SLO within browser context

[Ray Bon]

Paul,

I think phpCas will do logout replication if it is configured with the ips of 
cluster members. Not sure about other clients.
In a 'true' clustered environment, the user sessions are shared among cluster 
members. Thus, any host receiving the logout request will propagate to other 
cluster members.

Ray

On Tue, 2020-06-16 at 22:21 -0700, Paul Roemer wrote:

Hey guys,

I just ran into the SLO + loadbalancer issue as some of our CAS clients are 
clustered. Now, I wonder if it is possible to send the POST logout requests to 
the services participating at the current SSO session from within the 
browser/from client side instead of sending them from the CAS server.

If that is possible, I expect the load balancer issue is solved without further 
adjustments as it will redirect the request to the correct node in case of a 
clustered CAS client.

What are your thougts?

Cheers,
  Paul

--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/9afe02a69be0925bdca3ca676ef8caaa0cd808aa.camel%40uvic.ca.

Re: [cas-user] SLO within browser context

[Jérôme LELEU]

Hi,

Yes, you can. This is called "front channel". You can configure that at the
service level.
See:
https://apereo.github.io/cas/6.1.x/installation/Logout-Single-Signout.html#front-channel
Thanks.
Best regards,
Jérôme


Le mer. 17 juin 2020 à 07:22, Paul Roemer  a écrit :

>
> Hey guys,
>
> I just ran into the SLO + loadbalancer issue as some of our CAS clients
> are clustered. Now, I wonder if it is possible to send the POST logout
> requests to the services participating at the current SSO session from
> within the browser/from client side instead of sending them from the CAS
> server.
>
> If that is possible, I expect the load balancer issue is solved without
> further adjustments as it will redirect the request to the correct node in
> case of a clustered CAS client.
>
> What are your thougts?
>
> Cheers,
>   Paul
>
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> ---
> You received this message because you are subscribed to the Google Groups
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cas-user+unsubscr...@apereo.org.
> To view this discussion on the web visit
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/95830dcf-aa6a-44df-8c7e-7d84d517f83an%40apereo.org
> 
> .
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAP279LzsM0qg5donJaN4yVkmf8_kFaxmeJh7UX3ChiE4aK0hpQ%40mail.gmail.com.