Totally agree...
 i already have cold-feet as i am reading more into it....
As I am customizing the login page, i will probably accept your 
suggestion.:)
May i ask another question?
I have an Application A which is Java based and Application B which is 
Python based. Application B calls Application A quite a lot by calling A's 
API; e.x. 
http://applicationA.corp.com/TaskManager?taskId=1&&isCompleted=true

Since i turned on SSO, right now Application A is https and unless someone 
logged in, it's not possible to make the call anymore as it's a 
application-to-application interaction. Do you have something in mind thus 
i can keep this behavior normal as before?
I would say millions of thank you. And i hope people who is struggling like 
me can benefit from all this!

在 2017年8月28日星期一 UTC-4下午1:41:46,rbon写道:
>
> Sophie,
>
> CAS definitely has a lot of moving parts. Patience, small steps and lots 
> of testing.
>
> If I understand correctly, your client application has a login form. You 
> should be able to use REST to pass that user's credentials to the CAS 
> server without having to redirect.
> If that is the route you choose, you will have to keep track of the user's 
> session and associate it with the TGT. You may also have to manage session 
> expiration. This sounds like a lot of work.
> If your client application does not have a login form, you will have to 
> retrieve the user's login name and password from somewhere. This sounds 
> risky.
>
> Is there a reason why you do not want to go through the redirect?
>
> If the user is already logged in through CAS the redirect will be very 
> fast, the user will not notice. If you are concerned about the look of the 
> login page, that can be customized to look like your application.
>
> Ray
>
> On Mon, 2017-08-28 at 10:01 -0700, SOPHIE Fang wrote:
>
> Thank you for the speedy answer! Really Appreciate it!!
> My questions might sound pretty silly to someone already quite familiar 
> with the CAS Protocal. But still newbie as i am, may i ask..: 
> Why the REST Protocol sounds like it's for application-to-application 
> authentication. Will it really help my case?
>  What i am trying to do-- Instead of redirecting to the cas login page 
> everytime user hit my client application, user can just stay in my client 
> application and hit login then somehow get authenticated via CAS while 
> staying in the same page.  Do you know the step by step how to achieve 
> this? As i know about CAS so far, there is no baby sitting step by step. 
> It's more like playing a puzzles gathering people's experience here and 
> there.
>
> 在 2017年8月28日星期一 UTC-4上午11:44:05,rbon写道: 
>
> Is this what you are looking for?
> https://apereo.github.io/cas/5.1.x/protocol/REST-Protocol.html
>
> Ray
>
> On Mon, 2017-08-28 at 07:21 -0700, SOPHIE Fang wrote:
>
> Did you find the way to do it? 
> Thx!
>
> 在 2017年3月21日星期二 UTC-4上午10:24:34,Hao Wu写道: 
>
> Hello all,
> I want to embed the login form in the client page, without reidrection, 
> have googled for some solutions about 3.x or 4.x, is there any solutions 
> for 5.x? Thanks
>
>
> -- 
> Ray Bon
> Programmer analyst
> Development Services, University Systems
> 2507218831 | CLE 023 | [email protected]
>
>
> -- 
> Ray Bon
> Programmer analyst
> Development Services, University Systems
> 2507218831 | CLE 023 | [email protected] <javascript:>
>
>

-- 
- 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/1fafe227-adbf-4977-ac07-b5760fdb3cf4%40apereo.org.

Reply via email to