修改让cas支持客户端自定义登陆页面----服务器篇-

paypal登陆  时间:2021-01-09  阅读:()

 让CAS支持客户端自定义登陆页面——服务器篇- [De velopment]

2009-03-23

声明 时请以超形式标明文章原始出处和作者信息及本声明fallenlord.blogbus./logs/36907044.html

上篇《让CAS支持客户端自定义登陆页面——原理篇》讲述了一些修改的理论基础这篇讲解如何对C AS服务器端进行修改。

修改需要基于几个基本原则

1 . 不影响原有统一登陆界面功能

2. 客户端应尽量保持简单

3. 尽量保证原有功能的完整性和安全性

对于第三点 必须事先说明将登陆页面放到客户端本身就是降低了 CAS安全性这意味着作为服务向外发布的CAS服务器中的用户密码有可能由于客户端的不安全性而导致泄露整个CAS系统成为了一个“水桶形态”整个CAS体系的安全性将取决于所有客户端中安全性最低的一个。这也是CAS官方一直不推荐的方式。

接下来我们讲解服务器端修改的详细过程

首先修改/WEB-IN F/web.xml  为cas增加一个/remoteLogin的映射

<servl et-mappi ng>

<servlet-n ame>c as</s ervlet-n ame>

<url-pattern>/remoteLogin</url-pattern>

</servl et-mapping>

然后修改cas-servlet.xml文件 增加我们对/remoteLogin映射的处理 需要增加一个新流程<bean id="handlerMappingB" class="org.springframework.web.servlet.handler.SimpleUrlHandlerMappi ng ">

<property name="mappings">

<props>

<prop key="/login">loginControl ler</prop>

<prop key="/remoteLogin">remoteControl ler</prop>

</props>

</property>

<property name="interceptors">

<l ist>

<ref bean="localeChangeInterceptor" />

</list>

</property>

</b ea n>

然后在cas-servlet.xml文件中添加我们上面所配置的remoteController的bean

<!--增加远程控制者 允许以/remote请求启动remote控制流程-->

<bean id="remoteLoginControl ler"class="org.springframework.webflow.executor.mvc.FlowController"p:flowExecutor-ref="remoteLoginFlowExecutor"p:defaultFlowId="remoteLogin-webflow">

<property name="argumentHandl er">

<bean class="org.springframework.webflow.executor.support.RequestParameterFlowExecutorArgumentHandler"p:flowExecutionKeyArgu mentName="lt"

p:defaultFlowId="remoteLogin-webflow" />

</property>

</b ea n>

<flow:executor id="remoteLoginFlowExecutor" registry-ref="remoteLoginFlowRegistry">

<flow:execution-attributes>

<flow:alwaysRedirectOnPause value="false"/>

</flow:execution-attributes>

</flow:executor>

<flow:registry id="remoteLoginFlowRegistry">

<flow:location path="/WEB-INF/remoteLogin-webflow.xml"/>

</flow:registry>

可以看到上面将请求指向了webflow配置文件/WEB-IN F/remoteLogin-webflow.xml文件 我们需要创建此文件并配置其成为我们所需的流程 以下是remoteLogin-webflow.xml全文

<?xml version="1 .0" encoding="UTF-8"?>

<flow xmlns=".springframework.org/schema/webflow"xmlns:xsi=".w3.org/2001/XMLSchema-instance"xsi :schemaLocation="

.springframework.org/schema/webflow

.springframework.org/schema/webflow/spring-webflow-1 .0.xsd">

<start-state idref="remoteLogin"/>

<!--远程登陆主要Action -->

<action-state id="remoteLogin">

<action bean="remoteLoginAction" />

<transition on="error" to="remoteCal lbackView" />

<transition on="submit" to="bindAndValidate" />

<transition on="checkTicketGrantingTicket" to="ticketGrantingTicketExistsCheck" />

</action-state>

<!--远程回调页面 主要以JavaScript的方式回传一些参数用 -->

<end-state id="remoteCal lbackView" view="remoteCallbackView" />

<decision-state id="ticketGrantingTicketExistsCheck">

<if test="${flowScope.ticketGrantingTicketId != nul l}" then="hasServiceCheck"else="gat ewayRequ estCh eck" />

</decision-state>

<decision-state id="gatewayRequestCheck">

<if test="${external Context.requestParameterMap['gateway'] != ''&amp;&amp; externalContext.re questParameterMap['gateway'] != null&amp;&amp; flowScope.service != nul l}" then="redirect" else="re moteCal lbackView" />

</decision-state>

<decision-state id="hasServiceCheck">

<if test="${flowScope.service != nul l}" then="generateServiceTicket" else="remoteCal lbackView"/>

</decision-state>

<!--

The "warn" action makes the determination of whether to redirect directly to the requested service or display the "confirmation" page to go back to the server.

-->

<decision-state id="warn">

<if test="${flowScope.warnCookieValue}" then="showWarningView" else="redirect" /></decision-state>

<action-state id="bindAndVal idate">

<action bean="authenticationViaFormAction" />

<transition on="success" to="submit" />

<transition on="error" to="remoteCal lbackView" />

</action-state>

<action-state id="submit">

<action bean="authenticationViaFormAction"method="submit" />

<transition on="warn" to="warn" />

<transition on="success" to="sendTicketGrantingTicket" />

<transition on="error" to="remoteCal lbackView" />

</action-state>

<action-state id="sendTicketGrantingTicket">

<action bean="sendTicketGrantingTicketAction" />

<transition on="success" to="serviceCheck" />

</action-state>

<decision-state id="serviceCheck">

<if test="${flowScope.service != nul l}" then="generateServiceTicket"else="remoteCal lbackView" />

</decision-state>

<action-state id="generateServiceTicket">

<action bean="generateServiceTicketAction" />

<transition on="success" to ="warn" />

<transition on="error" to="remoteCal lbackView" />

<transition on="gateway" to="redirect" />

</action-state>

<!--

The "showWarningView" end state is the end state for when the user has requested privacy settings (to be "warned") to be turned on. It delegates to a view defines in default_views.properties that display the "Please cl ick here to go to the service."message.

-->

<end-state id="showWarningView" view="casLoginConfirmView" />

<!--

The "redirect" end state al lows CAS to properly end the workflow whi le sti l l redirecting the user back to the service required.

-->

<end-state id="redirect" view="bean:dynamicRedirectViewSelector" />

<end-state id="viewServiceErrorView" view="viewServiceErrorView" />

<end-state id="viewServiceSsoErrorView" view="viewServiceSsoErrorView" />

<global-transitions>

<transition to="viewServiceErrorView" on-exception="org.springframework.webflow.execution.repository.NoSuchFlowExecuti onException" />

<transition to="viewServiceSsoErrorView" on-

exception="org.jasig.cas.services.UnauthorizedSsoServiceException" />

<transition to="viewServiceErrorView" on-exception="org.jasig.cas.services.UnauthorizedServiceException" />

</global-transitions>

</flow>

以上文件根据原login-webflow.xml文件修改黄色背景为修改部分。可以看到我们在流程中增加了 r emoteLogin Action节点和remoteCallback View节点 下面我们配置remoteLogin节点

在/WEB-IN F/cas-servlet.xml文件中增加remoteLoginAction配置

<bean id="remoteLoginAction"class=".baidu.cas.web.flow.RemoteLoginAction"p:argu mentExtractors-ref="argumentExtractors"p:warnCookieGenerator-ref="warnCookieGenerator"p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator" />

同时创建com.baidu.cas.web.flow.RemoteLoginAction类

*

*远程登陆票据提供Action.

*根据InitialFlowSetupAction修改.

* 由于InitialFlowSetupAction为final类 因此只能将代码复制过来再进行修改.

*

* author GuoLin

*/publ ic class RemoteLoginAction extends AbstractAction {

/** CookieGenerator for the Warnings. */

NotNul l

private CookieRetrievingCookieGenerator warnCookieGenerator;

/** CookieGenerator for the TicketGrantingTickets. */

NotNul l private CookieRetrievingCookieGenerator ticketGrantingTicketCookieGenerator;/** Extractors for finding the service. */

NotEmpty private List<ArgumentExtractor> argumentExtractors;

/** Boolean to note whether we've set the values on the generators or not. */private boolean pathPopulated = false;protected Event doExecute(final RequestContext context) throws Exception {final HttpServletRequest request =WebUti ls.getHttpServletRequest(context);if (!this.pathPo pul ated) {final String contextPath = context.getExternal Context().getContextPath() ;final String cookiePath = StringUti ls.hasText(contextPath) ? contextPath : "/";logger.info("Setting path for cookies to: " +cookiePath);this.warnCookieGenerator.setCookiePath(cookiePath) ;this.ticketGrantingTicketCookieGenerator.setCookiePath(cookiePath);this.pathPopulated = true;

}context.getFlowScope().put("ticketGrantingTicketId",this.ticketGrantingTicketCookieGenerator.retrieveCookieValue(request)) ;context.getFlowScope().put("warnCookieValue",

Boolean.valueOf(this.warnCookieGenerator.retrieveCookieValue(request))) ;final Service service =WebUti ls.getService(this.argumentExtractors, context);if (service != nul l &&logger.isDebugEnabled()) {logger.debug("Placing service in FlowScope: " + service.getId());

}context.getFlowScope().put("service", service) ;

//客户端必须传递loginUrl参数过来否则无法确定登陆目标页面if (StringUti ls.hasText(request.getParameter("loginUrl"))) {context.getFlowScope().put("remoteLoginUrl", request.getParameter("loginUrl"));

} else {request.setAttribute("remoteLoginMessage", "loginUrl parameter must be supported.") ;return error();

}

//若参数包含submit则进行提交否则进行验证if (StringUti ls.hasText(request.getParameter("submit"))) {return result("submit");

} else {return result("checkTicketGrantingTicket");

}

}publ ic void setTicketGrantingTicketCookieGenerator(final CookieRetrievingCookieGenerator ticketGrantingTicketCookieGenerator) {this.ticketGrantingTicketCookieGenerator = ticketGrantingTicketCookieGenerator;

}publ ic void setWarnCookieGenerator(final CookieRetrievingCookieGenerator warnCookieGenerator) {this.warnCookieGenerator =warnCookieGenerator;

}publ ic void setArgumentExtractors(

天上云月付572元,起香港三网CN2直连,独立服务器88折优惠,香港沙田机房

天上云怎么样?天上云隶属于成都天上云网络科技有限公司,是一家提供云服务器及物理服务器的国人商家,目前商家针对香港物理机在做优惠促销,香港沙田机房采用三网直连,其中电信走CN2,带宽为50Mbps,不限制流量,商家提供IPMI,可以自行管理,随意安装系统,目前E3-1225/16G的套餐低至572元每月,有做大规模业务的朋友可以看看。点击进入:天上云官方网站天上云香港物理机服务器套餐:香港沙田数据中...

Pacificrack:新增三款超级秒杀套餐/洛杉矶QN机房/1Gbps月流量1TB/年付仅7美刀

PacificRack最近促销上瘾了,活动频繁,接二连三的追加便宜VPS秒杀,PacificRack在 7月中下旬已经推出了五款秒杀VPS套餐,现在商家又新增了三款更便宜的特价套餐,年付低至7.2美元,这已经是本月第三波促销,带宽都是1Gbps。PacificRack 7月秒杀VPS整个系列都是PR-M,也就是魔方的后台管理。2G内存起步的支持Windows 7、10、Server 2003\20...

Webhosting24:$1.48/月起,日本东京NTT直连/AMD Ryzen 高性能VPS/美国洛杉矶5950X平台大流量VPS/1Gbps端口/

Webhosting24宣布自7月1日起开始对日本机房的VPS进行NVMe和流量大升级,几乎是翻倍了硬盘和流量,价格依旧不变。目前来看,日本VPS国内过去走的是NTT直连,服务器托管机房应该是CDN77*(也就是datapacket.com),加上高性能平台(AMD Ryzen 9 3900X+NVMe),还是有相当大的性价比的。此外在6月30日,又新增了洛杉矶机房,CPU为AMD Ryzen 9...

paypal登陆为你推荐
全能虚拟主机时代互联的全能云虚拟主机怎么样,稳不稳定,速度怎么样的?域名购买为什么要购买域名,域名是干嘛用的?香港虚拟空间香港虚拟主机空间哪家最好西安虚拟主机西安云主机/云主机与vps有哪些区别长沙虚拟主机长沙IDC,求长沙本地虚拟主机,大伙推荐推荐万网域名怎样设置域名解析 万网域名解析图解域名反查icp备案 反查ip反查域名如何从ip地址查域名如何注册域名怎么去申请域名域名到期查询您的域名已经到期,请联系您的服务商续费怎么办?
国外域名 二级域名申请 stablehost 256m内存 ssh帐号 天猫双十一抢红包 国内php空间 京东商城双十一活动 太原联通测速平台 电子邮件服务器 免费网页空间 上海联通宽带测速 卡巴斯基免费试用版 宿迁服务器 香港ip 什么是dns server2008 iptables 达拉斯 电脑显示屏不亮但是主机已开机 更多