wso2-extensions / identity-inbound-auth-cas Goto Github PK

Dears ,
Greetings ,,, first i would like to appreciate your great work in the CAS connector .
i used it with WSO2 IS 5.2.0 and its working well , but when i upgrade it to 5.3.0 i faced some issues in redirection between client (my Application) and WSO2 (CAS server ) .
the error message that appears was :
"500 internal server error "

then i traced back the error log "wso2carbon.log" , but i can't find any type of error.
so kindly help me to make it work .
thanks in advance .

Description:
Add logout function to CAS authenticator

Related Issues:
https://wso2.org/jira/browse/ISCONNECT-77

Issue with CAS Protocol Proxy Support. Not fully implemented as per Specification.
We need support.

https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html

/serviceValidate [ service ticket validation [CAS 2.0] ]

1. No support for pgtUrl [OPTIONAL]

• the URL of the proxy callback. Discussed in Section 2.5.4. As a HTTP request parameter, the “pgtUrl” value MUST be URL-encoded as described in Section 2.2 of RFC 1738 [4].

2. Response doesn't contain
   cas:proxyGrantingTicketPGT...</cas:proxyGrantingTicket>

/proxyValidate [ service/proxy ticket validation [CAS 2.0] ]

1. No support for pgtUrl [OPTIONAL]

• the URL of the proxy callback. Discussed in Section 2.5.4. As a HTTP request parameter, the “pgtUrl” value MUST be URL-encoded as described in Section 2.2 of RFC 1738 [4].

2. Response doesn't contain
   cas:proxyGrantingTicketPGT...</cas:proxyGrantingTicket>

3. Response doesn't contain
   cas:proxies
   cas:proxyhttps://proxy2/pgtUrl</cas:proxy>
   cas:proxyhttps://proxy1/pgtUrl</cas:proxy>
   </cas:proxies>

/proxy [ proxy ticket service [CAS 2.0] ]

Not implemented

/p3/serviceValidate [ service ticket validation [CAS 3.0] ]

Not implemented

/p3/proxyValidate [ service/proxy ticket validation [CAS 3.0] ]

Not implemented

Description:
Move the contributions provided for inbound CAS support, i18n enhancements to the login and redirect pages, and other changes.

Related Issues:
https://wso2.org/jira/browse/IDENTITY-3199

#16
Tag: https://github.com/wso2-extensions/identity-inbound-auth-cas/tree/v2.0.0

Description:
Based on this document :
https://docs.wso2.com/display/ISCONNECTORS/Configuring+CAS+Inbound+Authenticator
I created a Service Provider and configure all needed.
I need to some Claim like email address and mobile so i define this Claims in Claim Configuration section based on document.
Also i run the cas-client-webapp and configure that to work with my service provider.
But when i login with a user and return to client side the user attributes is null like below :

Suggested Labels:

Suggested Assignees:

Affected Product Version:

OS, DB, other environment details and versions:

Steps to reproduce:

Related Issues:

Description:
The issue is i am getting server error 500 in 2 cases.
Case 1: when the url that i want to be behind CAS is https://example.com/hello/ but i only configure CAS URL in the wso2 identity server - service provider to be https://example.com/.

Case 2: When i click on the logout i am fronted with the same error "server error 500"

ERROR {org.apache.catalina.core.StandardWrapperValve} - Servlet.service() for servlet [bridgeservlet] in context with path [/] threw exception
org.wso2.carbon.identity.application.authentication.framework.inbound.FrameworkRuntimeException: org.wso2.carbon.identity.application.authentication.framework.inbound.FrameworkRuntimeException: No IdentityProcessor found to process the request

Suggested Labels:
issue, 2.0.2, improvement

Suggested Assignees:
@Shakila @Kanapriya

Affected Product Version:
2.0.1, 2.0.2, wso2is-5.3.0, wso2is-5.6.0, wso2is-5.7.0

OS, DB, other environment details and versions:
Linux - Debian, Postgresql

Steps to reproduce:
I followed this guide https://docs.wso2.com/display/ISCONNECTORS/Configuring+CAS+Inbound+Authenticator
when i do any of the described issue on the top it breaks.

Related Issues:
wso2/product-is#3861

Description:

Dear members,
There is a need to implement SLO functionality for this extension.
I've started implementation, Please let me know what action you propose to take.

Best Regards.

Suggested Labels:
enhancement,