Question

我正在尝试使用Spring安全性和CAS实现一个应用程序，它在localhost上工作正常，但当我尝试从外部机器访问它时，它和应用程序需要身份验证，它也会重定向到localhost。

含义

我使用https://172.16.1.50:8443/isxannouncements/访问该应用程序当需要身份验证时，应该转到https://172.16.1.50:8443/cas/login/ 但它转到https://localhost:8443/isxannouncements/

哪个方法打破了申请流程。

我的配置是

安全cas.xml

<bean id="serviceProperties"
      class="org.springframework.security.cas.ServiceProperties">
    <property name="service"
              value="https://localhost:8443/isxannouncements/login"/>
</bean>
<!--
    Allows changing where the CAS Server and CAS Service are easily
    by specifying System Arguments or replacing the values only in one place.
    Could also use external properties file -->
<context:property-placeholder
        system-properties-mode="OVERRIDE" properties-ref="environment"/>
<util:properties id="environment">
    <prop key="cas.service.host">localhost:8443</prop>
    <prop key="cas.server.host">localhost:8443</prop>
</util:properties>

<!-- sends to the CAS Server, must be in entry-point-ref of security.xml -->
<bean id="casEntryPoint"
      class="org.springframework.security.cas.web.CasAuthenticationEntryPoint">
    <property name="serviceProperties" ref="serviceProperties"/>
    <property name="loginUrl" value="https://localhost:8443/cas/login" />
</bean>

<!-- authenticates CAS tickets, must be in custom-filter of security.xml -->
<bean id="casFilter"
      class="org.springframework.security.cas.web.CasAuthenticationFilter">
    <property name="authenticationManager" ref="authenticationManager"/>
    <property name="filterProcessesUrl" value="/login"/>
</bean>

<bean id="casAuthProvider" class="org.springframework.security.cas.authentication.CasAuthenticationProvider">
    <property name="ticketValidator" ref="ticketValidator"/>
    <property name="serviceProperties" ref="serviceProperties"/>
    <property name="key" value="isxannouncements"/>
    <property name="authenticationUserDetailsService" ref="DBUserServiceDetails"/>
    <property name="statelessTicketCache" ref="statelessTicketCache"/>
</bean>

<bean id="statelessTicketCache" class="org.springframework.security.cas.authentication.EhCacheBasedTicketCache">
    <property name="cache">
        <bean class="net.sf.ehcache.Cache"
              init-method="initialise" destroy-method="dispose">
            <constructor-arg value="casTickets"/>
            <constructor-arg value="50"/>
            <constructor-arg value="true"/>
            <constructor-arg value="false"/>
            <constructor-arg value="3600"/>
            <constructor-arg value="900"/>
        </bean>
    </property>
</bean>

<bean id="ticketValidator" class="org.jasig.cas.client.validation.Saml11TicketValidator">
    <constructor-arg value="https://localhost:8443/cas" />
    <property name="encoding" value="utf8" />
</bean>

<!-- Handles a Single Logout Request from the CAS Server must be in custom-filter of security.xml -->
<bean id="singleLogoutFilter" class="org.jasig.cas.client.session.SingleSignOutFilter"/>

和我的security.xml

<security:http pattern="/resources/images" security="none"/>
<security:http use-expressions="true" entry-point-ref="casEntryPoint">
    <security:intercept-url pattern="/login/*"
                            access="permitAll"/>
    <security:intercept-url pattern="/resources/**"
                            access="permitAll"/>
    <security:intercept-url pattern="/logout"
                            access="permitAll"/>
    <security:intercept-url pattern="/errors/**"
                            access="permitAll"/>
    <security:intercept-url pattern="/approve-announcement**"
                            access="hasRole('ROLE_USER')"/>
    <security:intercept-url pattern="/delete-announcement**"
                            access="hasRole('ROLE_USER')"/>
    <security:intercept-url pattern="/edit-announcement**"
                            access="hasRole('ROLE_USER')"/>
    <security:intercept-url pattern="/admin/**"
                            access="hasRole('ROLE_ADMIN')"/>
    <security:intercept-url pattern="/META-INF"
                            access="hasRole('ROLE_USER')"/>
    <security:access-denied-handler error-page="/errors/403"/>

    <security:custom-filter ref="singleLogoutFilter" before="LOGOUT_FILTER"/>
    <security:custom-filter ref="casFilter" position="CAS_FILTER"/>
    <security:port-mappings>
        <security:port-mapping http="8080" https="8443"/>
    </security:port-mappings>

    <security:logout logout-url="/logout"
                     logout-success-url="https://localhost:8443/cas/logout"/>
</security:http>
<security:authentication-manager alias="authenticationManager">
    <security:authentication-provider ref="casAuthProvider" />
</security:authentication-manager>

如何解决这个问题？

Answer 1

好的，我发现了一种解决方法，但我没有正确测试，

受此answer的启发，我做了以下

由于我有两个用户可能用来访问我的应用程序的域，因此获取用户使用的域的唯一方法是从请求中获取，然后将其返回给安全提供程序。

我创建了一个名为serviceProperties的bean并使用它而不是spring的serviceproperties，并且我覆盖了getService的方法，以根据用户访问应用程序的域名返回服务

然后我在Web Application Context上提供了这个bean，我传入了会话，我已经从Request中提取了域并将其放入Session中。

因此，当CasAuthenticationEntryPoint尝试获取服务时，我将从我附加的会话创建的服务URL传递给服务名称。

Answer 2

我们使用属性文件处理此问题。任何特定于某个环境的东西（即本地计算机与测试服务器）都应该在属性文件中。

例如，为每个环境创建属性文件，如下所示：

localhost.properties：

    cas.service.url=http://localhost/login

test.properties：

    cas.service.url=http://mytestserver/login

然后使用属性文件中的值配置spring security，而不是直接使用上面的值：

然后，您的构建过程将为每个环境设置一个目标，以便将相应的文件随机放入最终工件中。

Answer 3

CAS在域下工作。所以你应该使用cas.example.com并在cas.properties中定义它

CAS + Spring Security检测localhost

3 个答案: