subject:"\[cas\-user\] Re\: CAS not redirecting to service after successful authentication."

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2019-03-26 Thread Bryan Wooten

Is there a load balancer involved?

I see you have a mix of https and http in the configuration.

We had a similar issue with .Net. Our load balancer was not configured to
redirect http to https.

-Bryan

On Tue, Mar 26, 2019 at 4:30 PM Pablo Vidaurri  wrote:

> Have you found a solution for this? I'm using a java client also using
> saml11 filter and I cant get my cas server to redirect back to my
> application after login
>
>
>
> On Monday, May 7, 2018 at 9:12:34 AM UTC-5, Neha Gupta wrote:
>>
>> Dear All,
>>
>> I am trying to integrate CAS with ASP.NET application.
>> Everything is working fine but CAS is not able to redirect to the
>> destination service and showing its own logged in page.
>>
>> Final URL is: - https://idiv-dev1:8443/cas/login?TARGET=
>> *http%3a%2f%2flocalhost%3a60397%2f*
>>
>> where in TARGET my service URL is defined where i want CAS to redirect .
>>
>> Following configuration i have done in "*web.config*" file: -
>>
>> *> casServerLoginUrl="https://idiv-dev1:8443/cas/login;
>> casServerUrlPrefix="https://idiv-dev1:8443/cas/;
>> serverName="http://localhost:60397/;
>> notAuthorizedUrl="~/NotAuthorized.aspx"
>> redirectAfterValidation="true"
>>  renew="false"
>> singleSignOut="true"
>> ticketValidatorName="Saml11"
>> serviceTicketManager="CacheServiceTicketManager"
>> * />*
>>
>> * *
>>   https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />
>> **
>>
>> Along with this configuration i have also mentioned in "*FilterConfig.cs*"
>> below two lines: -
>>
>> filters.Add(new System.Web.Mvc.AuthorizeAttribute());
>> filters.Add(new RequireHttpsAttribute());
>>
>>
>> Please let me know where is the problem as i have no clue.
>>
>> PS: - I have registered the service with CAS and also below service is
>> present which authorizes all services to pass through CAS: -
>> {
>>   "@class" : "org.apereo.cas.services.RegexRegisteredService",
>>   "serviceId" : "*^(https|imaps|http)://.**",
>>   "name" : "Apereo",
>>   "theme" : "apereo",
>>   "id" : 1002,
>>   "description" : "Apereo foundation sample service",
>>   "evaluationOrder" : 1
>>"accessStrategy" : {
>> "@class" :
>> "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
>> "enabled" : true,
>> "ssoEnabled" : true
>>   }
>> }
>>
>>
>>
>>
>> Regards
>> Neha Gupta
>>
> --
> - 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/982757c8-ec4f-4625-a944-5700f7edaa63%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/CAG9x2GWRH18BDF%2BpBnJFe6Pd1aeUbi4GuH1603pbTZukoodDwg%40mail.gmail.com.

[cas-user] Re: CAS not redirecting to service after successful authentication.

2019-03-26 Thread Pablo Vidaurri

Have you found a solution for this? I'm using a java client also using 
saml11 filter and I cant get my cas server to redirect back to my 
application after login



On Monday, May 7, 2018 at 9:12:34 AM UTC-5, Neha Gupta wrote:
>
> Dear All,
>
> I am trying to integrate CAS with ASP.NET application.
> Everything is working fine but CAS is not able to redirect to the 
> destination service and showing its own logged in page.
>
> Final URL is: - https://idiv-dev1:8443/cas/login?TARGET=
> *http%3a%2f%2flocalhost%3a60397%2f*
>
> where in TARGET my service URL is defined where i want CAS to redirect .
>
> Following configuration i have done in "*web.config*" file: -
>
> * casServerLoginUrl="https://idiv-dev1:8443/cas/login; 
> casServerUrlPrefix="https://idiv-dev1:8443/cas/; 
> serverName="http://localhost:60397/; 
> notAuthorizedUrl="~/NotAuthorized.aspx" 
> redirectAfterValidation="true"
>  renew="false" 
> singleSignOut="true" 
> ticketValidatorName="Saml11" 
> serviceTicketManager="CacheServiceTicketManager"
> * />*
>
> * *
>   https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />
> **
>
> Along with this configuration i have also mentioned in "*FilterConfig.cs*" 
> below two lines: - 
>
> filters.Add(new System.Web.Mvc.AuthorizeAttribute());
> filters.Add(new RequireHttpsAttribute());
>
>
> Please let me know where is the problem as i have no clue.
>
> PS: - I have registered the service with CAS and also below service is 
> present which authorizes all services to pass through CAS: -
> {
>   "@class" : "org.apereo.cas.services.RegexRegisteredService",
>   "serviceId" : "*^(https|imaps|http)://.**",
>   "name" : "Apereo",
>   "theme" : "apereo",
>   "id" : 1002,
>   "description" : "Apereo foundation sample service",
>   "evaluationOrder" : 1
>"accessStrategy" : {
> "@class" : 
> "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
> "enabled" : true,
> "ssoEnabled" : true
>   }
> }
>
>
>
>
> Regards
> Neha Gupta
>

-- 
- 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/982757c8-ec4f-4625-a944-5700f7edaa63%40apereo.org.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-23 Thread Ray Bon

Neha,

I have not used ASP so am unfamiliar with its operation. Perhaps certificates
need to be added to ASP environment?
Do you have way to watch ASP network communications?

Ray

On Wed, 2018-05-23 at 11:27 +0200, N Technical Channel NS wrote:
Hello Ray,

Yes i am using self signed certificate and already added it.
My java application is working fine with CAS but not ASP.

What more can i try? Really stuck with the problem with no clue what to do next
:(

Regards
Neha Gupta

On Tue, May 15, 2018 at 7:16 PM, Ray Bon >
wrote:
Neha,

I have not used the .NET client. There may be more configuration that can be
done.
One possibility is certificate validity. For .NET client to connect to CAS
during ticket validation, CAS needs to verify client certificate.
Are you using self signed certificates? If so, they need to be added to the JVM
running CAS.

Ray

On Mon, 2018-05-14 at 04:13 -0700, Neha Gupta wrote:
Hello Ray,

Request you to please help me out with this.
Please let me know in case you need any other information.

Regards
Neha Gupta

On Wednesday, May 9, 2018 at 10:25:46 AM UTC+2, Neha Gupta wrote:
Hello Ray,

Yes that what is clear from the traces that service ticket are getting
generated but not validated. I have done all the configuration required in
ASP.NET application.
Infact i just included the "DotNetCasClient" package and everything was done
automatically. I just changed the values of some attributes like
casServerLoginUrl, casServerUrlPrefix etc.

Below is the link which i followed for doing the changes in
ASP.NET application: -
https://github.com/apereo/dotnet-cas-client#integration-instructions

I don't have any idea as what can be done to solve this problem and i would
greatly appreciate if your community can help me out to solve the issue.

I am attaching web.config file for reference here.

PS: - I don't have any intention of using any particular ticket validator.
Initially i tried with Cas20 but as it was not working so i switched to Saml11
which though working but not redirecting to the ASP.NET
application.

Regards
Neha Gupta

On Tuesday, May 8, 2018 at 6:39:44 PM UTC+2, rbon wrote:
Neha,

There may be other settings that need to be modified when switching from SAML11
to CAS20. ST are being created but not validated. Your ASP.NET
client is not configured correctly.

Ray

On Tue, 2018-05-08 at 03:56 -0700, Neha Gupta wrote:
Hello Andy,

Thanks for reply.
I was also wondering about the TARGET in the URL and i think its because of the
ticketValidatorName="Saml11" mentioned in the web.config file of
ASP.NET application and when i change the value of
"ticketValidatorName" to Cas10 or Cas20 then it does not work at all.Also
please find attached traces of the same.

Hope this will help.

Regards
Neha Gupta

On Tuesday, May 8, 2018 at 3:40:21 AM UTC+2, Andy Ng wrote:
Hi Neha,

Would like to know in which documentation do you know about the parameter
TARGET in
"https://idiv-dev1:8443/cas/login?TARGET=http%3a%2f%2flocalhost%3a60397%2f;, I
didn't see this parameter in the official documentation.
Maybe it is something related to ASP.NET?

Anyway, the usual parameter for defining service in CAS is "service", that
means your url should be
"https://idiv-dev1:8443/cas/login?service=http%3a%2f%2flocalhost%3a60397%2f;

It is nice that you attached the debug log:
- I can see that the service is register successfully based on "", so your service registration
is correct.

Regarding the part related to ASP.NET, I have no idea so I
would not comment on that. But i think since you can login success, the
ASP.NET part should be fine as is.

Cheers!
- Andy

On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote:
Dear All,

I am trying to integrate CAS with ASP.NET application.
Everything is working fine but CAS is not able to redirect to the destination
service and showing its own logged in page.

Final URL is: -
https://idiv-dev1:8443/cas/login?TARGET=http%3a%2f%2flocalhost%3a60397%2f

where in TARGET my service URL is defined where i want CAS to redirect .

Following configuration i have done in "web.config" file: -

https://idiv-dev1:8443/cas/login;
casServerUrlPrefix="https://idiv-dev1:8443/cas/;
serverName="http://localhost:60397/;
notAuthorizedUrl="~/NotAuthorized.aspx"
redirectAfterValidation="true"
renew="false"
singleSignOut="true"
ticketValidatorName="Saml11"
serviceTicketManager="CacheServiceTicketManager"
/>

https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />

Along with this configuration i have also mentioned in "FilterConfig.cs" below
two lines: -

filters.Add(new System.Web.Mvc.AuthorizeAttribute());
filters.Add(new RequireHttpsAttribute());

Please let me know where is the problem as i have no clue.

PS: - I have registered the service with CAS and also

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-23 Thread N Technical Channel NS

Hello Ray,

Yes i am using self signed certificate and already added it.
My java application is working fine with CAS but not ASP.

What more can i try? Really stuck with the problem with no clue what to do
next :(


Regards
Neha Gupta


On Tue, May 15, 2018 at 7:16 PM, Ray Bon  wrote:

> Neha,
>
> I have not used the .NET client. There may be more configuration that can
> be done.
> One possibility is certificate validity. For .NET client to connect to CAS
> during ticket validation, CAS needs to verify client certificate.
> Are you using self signed certificates? If so, they need to be added to
> the JVM running CAS.
>
> Ray
>
> On Mon, 2018-05-14 at 04:13 -0700, Neha Gupta wrote:
>
> Hello Ray,
>
> Request you to please help me out with this.
> Please let me know in case you need any other information.
>
>
> Regards
> Neha Gupta
>
> On Wednesday, May 9, 2018 at 10:25:46 AM UTC+2, Neha Gupta wrote:
>
> Hello Ray,
>
> Yes that what is clear from the traces that service ticket are getting
> generated but not validated. I have done all the configuration required in
> ASP.NET application.
> Infact i just included the "DotNetCasClient" package and everything was
> done automatically. I just changed the values of some attributes like
> casServerLoginUrl, casServerUrlPrefix etc.
>
> Below is the link which i followed for doing the changes in ASP.NET
> application: -
> https://github.com/apereo/dotnet-cas-client#integration-instructions
>
> I don't have any idea as what can be done to solve this problem and i
> would greatly appreciate if your community can help me out to solve the
> issue.
>
> I am attaching web.config file for reference here.
>
> PS: - I don't have any intention of using any particular ticket validator.
> Initially i tried with Cas20 but as it was not working so i switched to
> Saml11 which though working but not redirecting to the ASP.NET
> application.
>
>
> Regards
> Neha Gupta
>
>
> On Tuesday, May 8, 2018 at 6:39:44 PM UTC+2, rbon wrote:
>
> Neha,
>
> There may be other settings that need to be modified when switching from
> SAML11 to CAS20. ST are being created but not validated. Your ASP.NET
> client is not configured correctly.
>
> Ray
>
> On Tue, 2018-05-08 at 03:56 -0700, Neha Gupta wrote:
>
> Hello Andy,
>
> Thanks for reply.
> I was also wondering about the TARGET in the URL and i think its because
> of the *ticketValidatorName="Saml11"* mentioned in the web.config file of
> ASP.NET application and when i change the value of "ticketValidatorName"
> to Cas10 or Cas20 then it does not work at all.Also please find attached
> traces of the same.
>
> Hope this will help.
>
>
> Regards
> Neha Gupta
>
>
>
>
> On Tuesday, May 8, 2018 at 3:40:21 AM UTC+2, Andy Ng wrote:
>
> Hi Neha,
>
> Would like to know in which documentation do you know about the parameter
> TARGET in "https://idiv-dev1:8443/cas/login?TARGET=
> *http%3a%2f%2flocalhost%3a60397%2f*", I didn't see this parameter in the
> official documentation.
> Maybe it is something related to ASP.NET?
>
> Anyway, the usual parameter for defining service in CAS is "service", that
> means your url should be "https://idiv-dev1:8443/cas/login?*service*
> =http%3a%2f%2flocalhost%3a60397%2f"
>
> It is nice that you attached the debug log:
> - I can see that the service is register successfully based on " registered service [^(https|imaps|http)://.*]>", so your service
> registration is correct.
>
> Regarding the part related to ASP.NET, I have no idea so I would not
> comment on that. But i think since you can login success, the ASP.NET
> part should be fine as is.
>
> Cheers!
> - Andy
>
>
> On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote:
>
> Dear All,
>
> I am trying to integrate CAS with ASP.NET application.
> Everything is working fine but CAS is not able to redirect to the
> destination service and showing its own logged in page.
>
> Final URL is: - https://idiv-dev1:8443/cas/login?TARGET=
> *http%3a%2f%2flocalhost%3a60397%2f*
>
> where in TARGET my service URL is defined where i want CAS to redirect .
>
> Following configuration i have done in "*web.config*" file: -
>
> * casServerLoginUrl="https://idiv-dev1:8443/cas/login;
> casServerUrlPrefix="https://idiv-dev1:8443/cas/;
> serverName="http://localhost:60397/;
> notAuthorizedUrl="~/NotAuthorized.aspx"
> redirectAfterValidation="true"
>  renew="false"
> singleSignOut="true"
> ticketValidatorName="Saml11"
> serviceTicketManager="CacheServiceTicketManager"
> * />*
>
> * *
>   https://idiv-dev1:84
> 43/cas/login" cookieless="UseCookies" />
> **
>
> Along with this configuration i have also mentioned in "*FilterConfig.cs*"
> below two lines: -
>
> filters.Add(new System.Web.Mvc.AuthorizeAttribute());
> filters.Add(new RequireHttpsAttribute());
>
>
> Please let me know where is the problem as i have no clue.
>
> PS: - I have registered the service with CAS and also below service is
> present which authorizes all services to pass through CAS: -
> {
>   "@class" :

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-15 Thread Ray Bon

Neha,

Ray

On Mon, 2018-05-14 at 04:13 -0700, Neha Gupta wrote:
Hello Ray,

Request you to please help me out with this.
Please let me know in case you need any other information.

Regards
Neha Gupta

On Wednesday, May 9, 2018 at 10:25:46 AM UTC+2, Neha Gupta wrote:
Hello Ray,

Below is the link which i followed for doing the changes in
ASP.NET application: -
https://github.com/apereo/dotnet-cas-client#integration-instructions

I don't have any idea as what can be done to solve this problem and i would
greatly appreciate if your community can help me out to solve the issue.

I am attaching web.config file for reference here.

Regards
Neha Gupta

On Tuesday, May 8, 2018 at 6:39:44 PM UTC+2, rbon wrote:
Neha,

There may be other settings that need to be modified when switching from SAML11
to CAS20. ST are being created but not validated. Your ASP.NET
client is not configured correctly.

Ray

On Tue, 2018-05-08 at 03:56 -0700, Neha Gupta wrote:
Hello Andy,

Hope this will help.

Regards
Neha Gupta

On Tuesday, May 8, 2018 at 3:40:21 AM UTC+2, Andy Ng wrote:
Hi Neha,

Anyway, the usual parameter for defining service in CAS is "service", that
means your url should be
"https://idiv-dev1:8443/cas/login?service=http%3a%2f%2flocalhost%3a60397%2f;

It is nice that you attached the debug log:
- I can see that the service is register successfully based on "", so your service registration
is correct.

Regarding the part related to ASP.NET, I have no idea so I
would not comment on that. But i think since you can login success, the
ASP.NET part should be fine as is.

Cheers!
- Andy

On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote:
Dear All,

I am trying to integrate CAS with ASP.NET application.
Everything is working fine but CAS is not able to redirect to the destination
service and showing its own logged in page.

Final URL is: -
https://idiv-dev1:8443/cas/login?TARGET=http%3a%2f%2flocalhost%3a60397%2f

where in TARGET my service URL is defined where i want CAS to redirect .

Following configuration i have done in "web.config" file: -

https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />

Along with this configuration i have also mentioned in "FilterConfig.cs" below
two lines: -

filters.Add(new System.Web.Mvc.AuthorizeAttribute());
filters.Add(new RequireHttpsAttribute());

Please let me know where is the problem as i have no clue.

PS: - I have registered the service with CAS and also below service is present
which authorizes all services to pass through CAS: -
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^(https|imaps|http)://.*",
"name" : "Apereo",
"theme" : "apereo",
"id" : 1002,
"description" : "Apereo foundation sample service",
"evaluationOrder" : 1
"accessStrategy" : {
"@class" : "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
"enabled" : true,
"ssoEnabled" : true
}
}

Regards
Neha Gupta

--
Ray Bon
Programmer analyst
Development Services,

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-14 Thread Neha Gupta

Hello Ray,

Request you to please help me out with this.
Please let me know in case you need any other information.


Regards
Neha Gupta

On Wednesday, May 9, 2018 at 10:25:46 AM UTC+2, Neha Gupta wrote:
>
> Hello Ray,
>
> Yes that what is clear from the traces that service ticket are getting 
> generated but not validated. I have done all the configuration required in 
> ASP.NET application.
> Infact i just included the "DotNetCasClient" package and everything was 
> done automatically. I just changed the values of some attributes like 
> casServerLoginUrl, casServerUrlPrefix etc.
>
> Below is the link which i followed for doing the changes in ASP.NET 
> application: -
> https://github.com/apereo/dotnet-cas-client#integration-instructions
>
> I don't have any idea as what can be done to solve this problem and i 
> would greatly appreciate if your community can help me out to solve the 
> issue.
>
> I am attaching web.config file for reference here.
>
> PS: - I don't have any intention of using any particular ticket validator. 
> Initially i tried with Cas20 but as it was not working so i switched to 
> Saml11 which though working but not redirecting to the ASP.NET 
> application.
>
>
> Regards
> Neha Gupta
>
>
> On Tuesday, May 8, 2018 at 6:39:44 PM UTC+2, rbon wrote:
>>
>> Neha,
>>
>> There may be other settings that need to be modified when switching from 
>> SAML11 to CAS20. ST are being created but not validated. Your ASP.NET 
>> client is not configured correctly.
>>
>> Ray
>>
>> On Tue, 2018-05-08 at 03:56 -0700, Neha Gupta wrote:
>>
>> Hello Andy, 
>>
>> Thanks for reply.
>> I was also wondering about the TARGET in the URL and i think its because 
>> of the *ticketValidatorName="Saml11"* mentioned in the web.config file 
>> of ASP.NET application and when i change the value of 
>> "ticketValidatorName" to Cas10 or Cas20 then it does not work at all.Also 
>> please find attached traces of the same.
>>
>> Hope this will help.
>>
>>
>> Regards
>> Neha Gupta
>>
>>
>>
>>
>> On Tuesday, May 8, 2018 at 3:40:21 AM UTC+2, Andy Ng wrote: 
>>
>> Hi Neha, 
>>
>> Would like to know in which documentation do you know about the parameter 
>> TARGET in "https://idiv-dev1:8443/cas/login?TARGET=
>> *http%3a%2f%2flocalhost%3a60397%2f*", I didn't see this parameter in the 
>> official documentation. 
>> Maybe it is something related to ASP.NET?
>>
>> Anyway, the usual parameter for defining service in CAS is "service", 
>> that means your url should be "https://idiv-dev1:8443/cas/login?*service*
>> =http%3a%2f%2flocalhost%3a60397%2f"
>>
>> It is nice that you attached the debug log:
>> - I can see that the service is register successfully based on "> registered service [^(https|imaps|http)://.*]>", so your service 
>> registration is correct.
>>
>> Regarding the part related to ASP.NET, I have no idea so I would not 
>> comment on that. But i think since you can login success, the ASP.NET 
>> part should be fine as is.
>>
>> Cheers!
>> - Andy
>>
>>
>> On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote: 
>>
>> Dear All, 
>>
>> I am trying to integrate CAS with ASP.NET application.
>> Everything is working fine but CAS is not able to redirect to the 
>> destination service and showing its own logged in page.
>>
>> Final URL is: - https://idiv-dev1:8443/cas/login?TARGET=
>> *http%3a%2f%2flocalhost%3a60397%2f*
>>
>> where in TARGET my service URL is defined where i want CAS to redirect .
>>
>> Following configuration i have done in "*web.config*" file: -
>>
>> *> casServerLoginUrl="https://idiv-dev1:8443/cas/login; 
>> casServerUrlPrefix="https://idiv-dev1:8443/cas/; 
>> serverName="http://localhost:60397/; 
>> notAuthorizedUrl="~/NotAuthorized.aspx" 
>> redirectAfterValidation="true"
>>  renew="false" 
>> singleSignOut="true" 
>> ticketValidatorName="Saml11" 
>> serviceTicketManager="CacheServiceTicketManager"
>> * />*
>>
>> * *
>>   https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />
>> **
>>
>> Along with this configuration i have also mentioned in "*FilterConfig.cs*" 
>> below two lines: - 
>>
>> filters.Add(new System.Web.Mvc.AuthorizeAttribute());
>> filters.Add(new RequireHttpsAttribute());
>>
>>
>> Please let me know where is the problem as i have no clue.
>>
>> PS: - I have registered the service with CAS and also below service is 
>> present which authorizes all services to pass through CAS: -
>> {
>>   "@class" : "org.apereo.cas.services.RegexRegisteredService",
>>   "serviceId" : "*^(https|imaps|http)://.**",
>>   "name" : "Apereo",
>>   "theme" : "apereo",
>>   "id" : 1002,
>>   "description" : "Apereo foundation sample service",
>>   "evaluationOrder" : 1
>>"accessStrategy" : {
>> "@class" : 
>> "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
>> "enabled" : true,
>> "ssoEnabled" : true
>>   }
>> }
>>
>>
>>
>>
>> Regards
>> Neha Gupta
>>
>>
>> -- 
>> Ray Bon
>> Programmer analyst
>> Development Services, University Systems
>> 2507218831 | CLE 019 |

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-09 Thread Neha Gupta

Hello Ray,

Yes that what is clear from the traces that service ticket are getting 
generated but not validated. I have done all the configuration required in 
ASP.NET application.
Infact i just included the "DotNetCasClient" package and everything was 
done automatically. I just changed the values of some attributes like 
casServerLoginUrl, casServerUrlPrefix etc.

Below is the link which i followed for doing the changes in ASP.NET 
application: -
https://github.com/apereo/dotnet-cas-client#integration-instructions

I don't have any idea as what can be done to solve this problem and i would 
greatly appreciate if your community can help me out to solve the issue.

I am attaching web.config file for reference here.

PS: - I don't have any intention of using any particular ticket validator. 
Initially i tried with Cas20 but as it was not working so i switched to 
Saml11 which though working but not redirecting to the ASP.NET application.


Regards
Neha Gupta


On Tuesday, May 8, 2018 at 6:39:44 PM UTC+2, rbon wrote:
>
> Neha,
>
> There may be other settings that need to be modified when switching from 
> SAML11 to CAS20. ST are being created but not validated. Your ASP.NET 
> client is not configured correctly.
>
> Ray
>
> On Tue, 2018-05-08 at 03:56 -0700, Neha Gupta wrote:
>
> Hello Andy, 
>
> Thanks for reply.
> I was also wondering about the TARGET in the URL and i think its because 
> of the *ticketValidatorName="Saml11"* mentioned in the web.config file of 
> ASP.NET application and when i change the value of "ticketValidatorName" 
> to Cas10 or Cas20 then it does not work at all.Also please find attached 
> traces of the same.
>
> Hope this will help.
>
>
> Regards
> Neha Gupta
>
>
>
>
> On Tuesday, May 8, 2018 at 3:40:21 AM UTC+2, Andy Ng wrote: 
>
> Hi Neha, 
>
> Would like to know in which documentation do you know about the parameter 
> TARGET in "https://idiv-dev1:8443/cas/login?TARGET=
> *http%3a%2f%2flocalhost%3a60397%2f*", I didn't see this parameter in the 
> official documentation. 
> Maybe it is something related to ASP.NET?
>
> Anyway, the usual parameter for defining service in CAS is "service", that 
> means your url should be "https://idiv-dev1:8443/cas/login?*service*
> =http%3a%2f%2flocalhost%3a60397%2f"
>
> It is nice that you attached the debug log:
> - I can see that the service is register successfully based on " registered service [^(https|imaps|http)://.*]>", so your service 
> registration is correct.
>
> Regarding the part related to ASP.NET, I have no idea so I would not 
> comment on that. But i think since you can login success, the ASP.NET 
> part should be fine as is.
>
> Cheers!
> - Andy
>
>
> On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote: 
>
> Dear All, 
>
> I am trying to integrate CAS with ASP.NET application.
> Everything is working fine but CAS is not able to redirect to the 
> destination service and showing its own logged in page.
>
> Final URL is: - https://idiv-dev1:8443/cas/login?TARGET=
> *http%3a%2f%2flocalhost%3a60397%2f*
>
> where in TARGET my service URL is defined where i want CAS to redirect .
>
> Following configuration i have done in "*web.config*" file: -
>
> * casServerLoginUrl="https://idiv-dev1:8443/cas/login; 
> casServerUrlPrefix="https://idiv-dev1:8443/cas/; 
> serverName="http://localhost:60397/; 
> notAuthorizedUrl="~/NotAuthorized.aspx" 
> redirectAfterValidation="true"
>  renew="false" 
> singleSignOut="true" 
> ticketValidatorName="Saml11" 
> serviceTicketManager="CacheServiceTicketManager"
> * />*
>
> * *
>   https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />
> **
>
> Along with this configuration i have also mentioned in "*FilterConfig.cs*" 
> below two lines: - 
>
> filters.Add(new System.Web.Mvc.AuthorizeAttribute());
> filters.Add(new RequireHttpsAttribute());
>
>
> Please let me know where is the problem as i have no clue.
>
> PS: - I have registered the service with CAS and also below service is 
> present which authorizes all services to pass through CAS: -
> {
>   "@class" : "org.apereo.cas.services.RegexRegisteredService",
>   "serviceId" : "*^(https|imaps|http)://.**",
>   "name" : "Apereo",
>   "theme" : "apereo",
>   "id" : 1002,
>   "description" : "Apereo foundation sample service",
>   "evaluationOrder" : 1
>"accessStrategy" : {
> "@class" : 
> "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
> "enabled" : true,
> "ssoEnabled" : true
>   }
> }
>
>
>
>
> Regards
> Neha Gupta
>
>
> -- 
> Ray Bon
> Programmer analyst
> Development Services, University Systems
> 2507218831 | CLE 019 | rb...@uvic.ca 
>
>

-- 
- 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

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-08 Thread Ray Bon

Neha,

There may be other settings that need to be modified when switching from SAML11 
to CAS20. ST are being created but not validated. Your ASP.NET client is not 
configured correctly.

Ray

On Tue, 2018-05-08 at 03:56 -0700, Neha Gupta wrote:
Hello Andy,

Thanks for reply.
I was also wondering about the TARGET in the URL and i think its because of the 
ticketValidatorName="Saml11" mentioned in the web.config file of ASP.NET 
application and when i change the value of "ticketValidatorName" to Cas10 or 
Cas20 then it does not work at all.Also please find attached traces of the same.

Hope this will help.


Regards
Neha Gupta




On Tuesday, May 8, 2018 at 3:40:21 AM UTC+2, Andy Ng wrote:
Hi Neha,

Would like to know in which documentation do you know about the parameter 
TARGET in 
"https://idiv-dev1:8443/cas/login?TARGET=http%3a%2f%2flocalhost%3a60397%2f;, I 
didn't see this parameter in the official documentation.
Maybe it is something related to ASP.NET?

Anyway, the usual parameter for defining service in CAS is "service", that 
means your url should be 
"https://idiv-dev1:8443/cas/login?service=http%3a%2f%2flocalhost%3a60397%2f;

It is nice that you attached the debug log:
- I can see that the service is register successfully based on "", so your service registration 
is correct.

Regarding the part related to ASP.NET, I have no idea so I 
would not comment on that. But i think since you can login success, the 
ASP.NET part should be fine as is.

Cheers!
- Andy


On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote:
Dear All,

I am trying to integrate CAS with ASP.NET application.
Everything is working fine but CAS is not able to redirect to the destination 
service and showing its own logged in page.

Final URL is: - 
https://idiv-dev1:8443/cas/login?TARGET=http%3a%2f%2flocalhost%3a60397%2f

where in TARGET my service URL is defined where i want CAS to redirect .

Following configuration i have done in "web.config" file: -

https://idiv-dev1:8443/cas/login;
casServerUrlPrefix="https://idiv-dev1:8443/cas/;
serverName="http://localhost:60397/;
notAuthorizedUrl="~/NotAuthorized.aspx"
redirectAfterValidation="true"
 renew="false"
singleSignOut="true"
ticketValidatorName="Saml11"
serviceTicketManager="CacheServiceTicketManager"
 />

 
  https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />


Along with this configuration i have also mentioned in "FilterConfig.cs" below 
two lines: -

filters.Add(new System.Web.Mvc.AuthorizeAttribute());
filters.Add(new RequireHttpsAttribute());


Please let me know where is the problem as i have no clue.

PS: - I have registered the service with CAS and also below service is present 
which authorizes all services to pass through CAS: -
{
  "@class" : "org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(https|imaps|http)://.*",
  "name" : "Apereo",
  "theme" : "apereo",
  "id" : 1002,
  "description" : "Apereo foundation sample service",
  "evaluationOrder" : 1
   "accessStrategy" : {
"@class" : "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
"enabled" : true,
"ssoEnabled" : true
  }
}




Regards
Neha Gupta



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

-- 
- 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/1525797572.1797.17.camel%40uvic.ca.

[cas-user] Re: CAS not redirecting to service after successful authentication.

2018-05-07 Thread Andy Ng

Hi Neha,

Would like to know in which documentation do you know about the parameter 
TARGET in "https://idiv-dev1:8443/cas/login?TARGET=
*http%3a%2f%2flocalhost%3a60397%2f*", I didn't see this parameter in the 
official documentation. 
Maybe it is something related to ASP.NET?

Anyway, the usual parameter for defining service in CAS is "service", that 
means your url should be "https://idiv-dev1:8443/cas/login?*service*
=http%3a%2f%2flocalhost%3a60397%2f"

It is nice that you attached the debug log:
- I can see that the service is register successfully based on "", so your service 
registration is correct.

Regarding the part related to ASP.NET, I have no idea so I would not 
comment on that. But i think since you can login success, the ASP.NET part 
should be fine as is.

Cheers!
- Andy


On Monday, 7 May 2018 22:12:34 UTC+8, Neha Gupta wrote:
>
> Dear All,
>
> I am trying to integrate CAS with ASP.NET application.
> Everything is working fine but CAS is not able to redirect to the 
> destination service and showing its own logged in page.
>
> Final URL is: - https://idiv-dev1:8443/cas/login?TARGET=
> *http%3a%2f%2flocalhost%3a60397%2f*
>
> where in TARGET my service URL is defined where i want CAS to redirect .
>
> Following configuration i have done in "*web.config*" file: -
>
> * casServerLoginUrl="https://idiv-dev1:8443/cas/login; 
> casServerUrlPrefix="https://idiv-dev1:8443/cas/; 
> serverName="http://localhost:60397/; 
> notAuthorizedUrl="~/NotAuthorized.aspx" 
> redirectAfterValidation="true"
>  renew="false" 
> singleSignOut="true" 
> ticketValidatorName="Saml11" 
> serviceTicketManager="CacheServiceTicketManager"
> * />*
>
> * *
>   https://idiv-dev1:8443/cas/login; cookieless="UseCookies" />
> **
>
> Along with this configuration i have also mentioned in "*FilterConfig.cs*" 
> below two lines: - 
>
> filters.Add(new System.Web.Mvc.AuthorizeAttribute());
> filters.Add(new RequireHttpsAttribute());
>
>
> Please let me know where is the problem as i have no clue.
>
> PS: - I have registered the service with CAS and also below service is 
> present which authorizes all services to pass through CAS: -
> {
>   "@class" : "org.apereo.cas.services.RegexRegisteredService",
>   "serviceId" : "*^(https|imaps|http)://.**",
>   "name" : "Apereo",
>   "theme" : "apereo",
>   "id" : 1002,
>   "description" : "Apereo foundation sample service",
>   "evaluationOrder" : 1
>"accessStrategy" : {
> "@class" : 
> "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
> "enabled" : true,
> "ssoEnabled" : true
>   }
> }
>
>
>
>
> Regards
> Neha Gupta
>

-- 
- 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/bf71cc99-1f5b-443b-9cc8-0b29dbcf2add%40apereo.org.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

[cas-user] Re: CAS not redirecting to service after successful authentication.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

Re: [cas-user] Re: CAS not redirecting to service after successful authentication.

[cas-user] Re: CAS not redirecting to service after successful authentication.

9 matches

Site Navigation

Mail list logo

Footer information