이 콘텐츠는 선택한 언어로 제공되지 않습니다.

8.7. Integrating with External Single Sign-on (SSO) Providers


Developers hosting applications on your OpenShift Enterprise instance may need to integrate their applications with external single sign-on (SSO) providers. To enable this, starting in OpenShift Enterprise 2.2.6 you can configure an SSO plug-in that broadcasts controller actions through ActiveMQ to be read and acted upon by an external SSO provider. These actions include:
  • Gear creation and deletion
  • Alias addition and removal
  • Environment variables addition, modification, and deletion
The external SSO provider can then listen for certain events occurring in the OpenShift Enterprise environment that are critical for utilizing the external SSO solution.

Procedure 8.21. To Install and Configure the SSO Plug-in:

  1. On the broker host, install the rubygem-openshift-origin-sso-activemq package:
    # yum install rubygem-openshift-origin-sso-activemq
  2. Before enabling this plug-in, you must add a new user, topic, and queue to ActiveMQ. Edit the /etc/activemq/activemq.xml file and add the following user in the appropriate section:
    <authenticationUser username="ssoinfo" password="ssoinfopasswd" groups="ssoinfo,everyone"/>
    Also add the following topic and queue to the appropriate sections:
    <authorizationEntry topic="ssoinfo.>" write="ssoinfo" read="ssoinfo" admin="ssoinfo" />
    <authorizationEntry queue="ssoinfo.>" write="ssoinfo" read="ssoinfo" admin="ssoinfo" />
  3. Restart ActiveMQ:
    # service activemq restart
  4. To enable the plug-in, copy the /etc/openshift/plugins.d/openshift-origin-sso-activemq.conf.example file to /etc/openshift/plugins.d/openshift-origin-sso-activemq.conf on the broker host:
    # cp /etc/openshift/plugins.d/openshift-origin-sso-activemq.conf.example \ /etc/openshift/plugins.d/openshift-origin-sso-activemq.conf
  5. In the /etc/openshift/plugins.d/openshift-origin-sso-activemq.conf file you just created, uncomment the last line specifying the /opt/rh/ruby193/root/etc/mcollective/client.cfg file:
    MCOLLECTIVE_CONFIG="/opt/rh/ruby193/root/etc/mcollective/client.cfg"
    Alternatively, edit the values for the ACTIVE_* parameters with the appropriate information for your environment.
  6. Restart the broker service for your changes take effect:
    # service openshift-broker restart
  7. Create a listener that will connect to ActiveMQ on the new topic that was added. The listener can be run on any system that can connect to the ActiveMQ server. The following is an example that simply echoes any messages received:
    #!/usr/bin/ruby
    
    require 'rubygems'
    require 'stomp'
    require 'yaml'
    
    c = Stomp::Client.new("ssoinfo", "ssoinfopasswd", "127.0.0.1", 61613)
    puts "Got stomp client, listening for messages on '/topic/ssoinfo':"
    c.subscribe('/topic/ssoinfo') { |msg|
            h = YAML.load(msg.body)
            puts "Message received: "
    	puts h.inspect
    }
    c.join
  8. Save and run your listener script. For example, if the script was saved at /root/listener.rb:
    # ruby /root/listener.rb
  9. To verify that the plug-in and listener are working, perform several application actions with the client tools or Management Console using a test user account. For example, create an application, add an alias, remove an alias, and remove the application. You should see messages reported by the listener script for each action performed.
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2026 Red Hat
맨 위로 이동