Rails/designe/SAML元数据不正确（不使用PingFederate）

Question

让我在这个问题的开头说，我是SAML的新手，几乎不了解它是如何工作的。

我正在使用gem和Rails 4应用程序来实现SSO。Rails应用程序充当服务提供商（SP）。为了测试我的设置，我创建了一个OneLogin开发者帐户，并使用以下属性设置了一个SAML测试连接器（IdP w/attr w/sign response）：

设置页

• 观众：mysubdomain.onelogin.com
• 收件人：http://mysubdomain.myapp.local:3000/saml/auth
• ACS（消费者）URL验证器：^http://mysubdomain.myapp.local:3000/saml/auth$
• ACS（消费者）网址：http://mysubdomain.myapp.local:3000/saml/auth
• 单个注销URL：http://mysubdomain.myapp.local:3000/saml/idp_sign_out

SSO选项卡

>

发卡机构URL：https://app.onelogin.com/saml/metadata/589819

SAML 2.0endpoint（HTTP）：https://mysubdomain.onelogin.com/trust/saml2/http-post/sso/589819

SLOendpoint（HTTP）：https://mysubdomain.onelogin.com/trust/saml2/http-redirect/slo/589819

SAML签名算法：SHA-1

SHA指纹：60:9D:18:56:B9:80:D4:25:63:C1:CC:57:6D:B9:06:7C:78:BB:2C:F1

十、 509证书：

-----开始证书------MIIEFzCCAv gAwIBAgIUQYRVa1MQpUh0gJaznmXSF/SPqnowDQYJKoZIhvcNAQEF bqawdelmakga1uebhmcvvmxetapbngnvbbaomcezpcm1qbgf5mruwewydvqqqldaxp bmvmb2dpbizfaxhzadbgnvbammfk9uxvz2luiefjy291bnqgoti1mzewhhcn mtywotixmtu0nzqwwwjbymqwcqydvqgewjvuzerma8g a1uecgwirm lybvbsyxkxftatbgnvbasmde9uzuxvz2luielkudefmb0ga1ueawwT25LTG9NAW4GQWNWJB3VUDCA5MJUZMTCCASIWDQYJKOZIHVCNAQEBBQADGGEGAPDCC AQOCGGEGBALGGOCBJ0CIHM3UKLWICOFPHOTZJW1XPADNYNAVPTBCL7WE5 sLBoQ ZF oZ7Dl wRW6DHMJCl9DdKcOaQA6/GR5BWT78IZ8HWMOKEQEPIH E0km6rKLYA8 M52VXTJGS8IQX60QVPQFEPMOA xg73OExfM7W5LnXwNz/PXGSR3LBIFOC76J SaTCFroV TSJV FOAYMW/lZrsS79KRIzA9I5XwUBe3bC8bsfQmZXgddCrkQUNSGGaS 7/jtFUlQ94 lAL l3yoAiNAE6 mt48qqmyLfkKibXvnZ8dwuO272wpY4fEM vFRyPyrtajqvhy3hyiq8dlw3omine5vecl8caweaaob2dcb1tambgnvhmbaf8eajaa mb0ga1uddgqwbbsbxuivtpxwohh2pupid tuykcetecetcblqydvr0jbignmiggbsx iuvTPxwOhh2pupID tuykceaefcowwdelmakga1ebhmcvmxetapbgnvbaom cezpcm1qbgf5mruwydvqqqqdaxpbmb2dpbizfaxhzadbgnvbammfk9uxv z2luiefjy291bngoti1mzgcfvwttkvm IDICWS55L0HF0J6P6MA4GA1UDDWeb/WQEAWIHGDANBGKQHKIG9W0BAQUFAAOCAQEQEAYBE 5d3zpLZ7fcf3l3rXYeIxcpN9D2YZCbxsrBhY2Am4YE9nN RAJXEDQERBNTPAYCZVFHNXEXRO1N7WXWTMOSIYE7SY2XZF 3feQreF25atnn4tzVhxYONaX1njZMIt/TNa7A9aeDfHSD vwSuYYB hGxKT6HOkEAEBiXCZ/FcVNiB0D8bRwQhiJ3BTzXDfqHrmq8QYdn3Ejlqo62vMl6W XEMXUYV6CUC64AP6E XTEQI1E8YB5R8GTTS3Y1OA2D6YYCYVJ20 Hi7IWAqXC EFQSTQ xb7foq2rat39cepnu1soarveydmwyiavnf3hoydbybjjsawancq==----结束证书-----

在我的devise.rb中，我有以下配置：

config.saml_create_user = false
config.saml_update_user = true
config.saml_default_user_key = :email
config.saml_session_index_key = :session_index
config.saml_use_subject = true
config.idp_settings_adapter = IdPSettingsAdapter
config.idp_entity_id_reader = DeviseSamlAuthenticatable::DefaultIdpEntityIdReader

这是我的IdPSettingsAdapter：

class IdPSettingsAdapter
    def self.settings(idp_entity_id)
        company = Company.find_by(idp_entity_id: idp_entity_id)

        if company.present?
            {
                assertion_consumer_service_url: company.assertion_consumer_service_url,
                assertion_consumer_service_binding: company.assertion_consumer_service_binding,
                name_identifier_format: company.name_identifier_format,
                issuer: company.issuer,
                idp_entity_id: company.idp_entity_id,
                authn_context: company.authn_context,
                idp_slo_target_url: company.idp_slo_target_url,
                idp_sso_target_url: company.idp_sso_target_url,
                idp_cert_fingerprint: company.idp_cert_fingerprint
            }
        else
            {}
        end
    end
end

请注意，我的用户模型联系人属于公司，SSO设置存储在公司模型中。

以下是我的saml路线：

devise_for :contacts, skip: :saml_authenticatable, controllers: {
    registrations: "registrations",
    sessions: "sessions",
    passwords: "passwords",
    confirmations: "confirmations"
}
devise_scope :contact do
    get '/sign_in' => 'sessions#new'
    get '/sign_out' => 'sessions#destroy'

    # SSO Routes
    get 'saml/sign_in' => 'saml_sessions#new', as: :new_user_sso_session
    post 'saml/auth' => 'saml_sessions#create', as: :user_sso_session
    get 'saml/sign_out' => 'saml_sessions#destroy', as: :destroy_user_sso_session
    get 'saml/metadata' => 'saml_sessions#metadata', as: :metadata_user_sso_session
    match 'saml/idp_sign_out' => 'saml_sessions#idp_sign_out', via: [:get, :post]
end

最后是我的SamlSessionsController：

require "ruby-saml"

class SamlSessionsController < SessionsController
    include DeviseSamlAuthenticatable::SamlConfig
    skip_before_filter :verify_authenticity_token, raise: false
    before_action :authorize_viewer, except: [:metadata]
    protect_from_forgery with: :null_session, except: :create

    def new
        idp_entity_id = Company.friendly.find(@_request.env['HTTP_HOST'].split('.')[0]).idp_entity_id
        request = OneLogin::RubySaml::Authrequest.new
        action = request.create(saml_config(idp_entity_id))
        redirect_to action
    end

    def metadata
        idp_entity_id = Company.friendly.find(@_request.env['HTTP_HOST'].split('.')[0]).idp_entity_id
        meta = OneLogin::RubySaml::Metadata.new
        render :xml => meta.generate(saml_config(idp_entity_id)), content_type: 'application/samlmetadata+xml'
    end

    def create
        @idp_entity_id = Company.friendly.find(@_request.env['HTTP_HOST'].split('.')[0]).idp_entity_id
        response = OneLogin::RubySaml::Response.new(params[:SAMLResponse], settings: saml_config(@idp_entity_id))

        if !response.is_valid?
            puts "SAML FAILED WITH ERROR: "
            puts response.errors
        end
        super
    end

    def idp_sign_out
        company = Company.friendly.find(request.subdomain.downcase)
        idp_entity_id = Company.friendly.find(@_request.env['HTTP_HOST'].split('.')[0]).idp_entity_id

        if params[:SAMLRequest] && Devise.saml_session_index_key
            saml_config = saml_config(idp_entity_id)
            logout_request = OneLogin::RubySaml::SloLogoutrequest.new(params[:SAMLRequest], settings: saml_config(idp_entity_id))
            resource_class.reset_session_key_for(logout_request.name_id)

            # binding.pry
            sign_out current_contact if contact_signed_in?
            redirect_to company.after_slo_url.present? ? company.after_slo_url : 'https://' + company.issuer
            # redirect_to generate_idp_logout_response(saml_config(idp_entity_id), logout_request.id)
        elsif params[:SAMLResponse]
            #Currently Devise handles the session invalidation when the request is made.
            #To support a true SP initiated logout response, the request ID would have to be tracked and session invalidated
            #based on that.
            if Devise.saml_sign_out_success_url
                redirect_to Devise.saml_sign_out_success_url
            else
                redirect_to action: :new
            end
        else
            head :invalid_request
        end
    end

    protected

    # Override devise to send user to IdP logout for SLO
    def after_sign_out_path_for(_)
        request = OneLogin::RubySaml::Logoutrequest.new
        request.create(saml_config)
    end

    def generate_idp_logout_response(saml_config, logout_request_id)
        OneLogin::RubySaml::SloLogoutresponse.new.create(saml_config, logout_request_id, nil)
    end
end

当我手动将OneLogin适配器中的设置映射到我的Company模型（参见屏幕截图）时，我能够使用OneLogin作为身份提供者（IdP）作为我的应用程序的用户进行身份验证。但是现在我需要向客户端提供代表应用程序设置的XML元数据。当我转到/saml/metadata.xml时，我得到以下配置，根据我的客户端，这是不正确的。客户端没有提供有关问题所在的任何进一步细节。如果这很重要的话，他们正在使用平联邦。

<?xml version='1.0' encoding='UTF-8'?>
<md:EntityDescriptor ID='_a3581975-b73d-4784-a106-bafd61e15f87' xmlns:md='urn:oasis:names:tc:SAML:2.0:metadata'>
    <md:SPSSODescriptor AuthnRequestsSigned='false' WantAssertionsSigned='false' protocolSupportEnumeration='urn:oasis:names:tc:SAML:2.0:protocol'>
        <md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</md:NameIDFormat>
        <md:AssertionConsumerService Binding='urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST' Location='https://mysubdomain.myapp.local:3000/saml/auth' index='0' isDefault='true'/>
    </md:SPSSODescriptor>
</md:EntityDescriptor>

我的问题是，我在这里做错了什么，我该如何纠正？正如我所说，我几乎不理解SAML是如何在后台工作的。

Answer 1

该元数据XML上没有定义EntityID。如果您尝试在验证工具上验证XML，您将获得

行：2 |列：0--

如果您查看ruby saml代码，则EntityID将添加到元数据XML中（如果设置不正确）。发行人已定义。你能确认是否提供了这些数据吗？也许是公司。我在IdPSettingsAdapter类中看到的颁发者有一个空值。