RSSO AR integration Error 623

Version 5
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy Single Sign On


    COMPONENT:

    Remedy Single Sign On


    APPLIES TO:

    All RSSO integrations with AR



    PROBLEM:

     

    AR Server - RSSO Integration give ARERR 623 error during login attempt

      

     

     


    CAUSE:

    Plugin and config files might not be accurate on AR server


    SOLUTION:

     

    The following steps help you to identify the root cause and provides a probable fix in configuration to solve the AR 623 error with a stack integrated with Remedy Single Sign-On (Remedy SSO). You may also perform the steps in case you do not see the complete application list after logging on.

      
       
    1. Check if the Remedy SSO Server is accessible from the BMC Remedy AR System Server.     
           
      1. Check if the Remedy SSO service URL is configured correctly in the rsso.cfg file located at {AR}/Conf/rsso.cfg. For example, D:\BMCSoftware\BMCARSystem\Conf\rsso.cfg.
      2.    
      3. Open the Remedy SSO service URL in a browser to check whether it is accessible from the BMC Remedy AR System Server.
      4.   
    2.  
    3. Check if the Remedy SSO plugin entry is set correctly in pluginsvr_config_xml.     
           
      1. Open the pluginsvr_config.xml located at {AR}/pluginsvr/pluginsvr_config.xml i.e “D:\BMCSoftware\BMCARSystem\pluginsvr\pluginsvr_config.xml” and check for the availability of the following entry.<plugin>
        <name>ARSYS.AREA.RSSO</name>
        <classname>com.bmc.rsso.plugin.area.RSSOPlugin</classname>
        <pathelement type="location">D:/BMCSoftware/BMCARSystem/pluginsvr/rsso-area-plugin-all.jar</pathelement>
        <userDefined>
        <configFile>D:/BMCSoftware/BMCARSystem/Conf/rsso.cfg</configFile>
        </userDefined>
        </plugin>
      2.    
      3. Make sure the file locations are correctly set.
      4.    
      5. Make sure the rsso-area-plugin-all.jar is present in the pluginsvr folder.
      6.    
      7. Comment out the ‘ARSYS.ARF.ATSSOCONFIRMPWD’ and ‘ARSYS.AREA.ATRIUMSSO’ entries as they are not needed if Remedy SSO is integrated with the stack.
      8.   
    4.  
    5. Make sure Plugin Server is running in the correct Plugin port (9999)     
           
      1. From Task Manager, make sure the Plugin Server is up and running.
      2.    
      3. Make sure the following Server-Plugin-Alias is present in ar.cfg. 
        Server-Plugin-Alias:AREA AREA onbmc-s:9999
      4.   
    6.  
    7. Check if the authenticated user is present in the AR User form.     
           
      1. The users which you authenticated against should be present in the AR User form.
      2.    
      3. Make sure the transformations are set correctly on the Remedy SSO Server, i.e if authenticated user is in lowercase. Remedy SSO may transform the user to UPPERCASE and hence the same user should also be present in UPPERCASE in the User form.
      4.   
    8.  
    9. Check if the entries are correctly set in the EA tab of the Server Information page of in ar.cfg.     
           
      • External-Authentication-RPC-Socket: 390695
      •    
      • Authentication-Chaining-Mode: 1
      •    
      • Use-Password-File: T
      •    
      • Crossref-Blank-Password: T
      •   
    10.  
    11. If EA chaining mode in the AR server is set to ARS-AREA (1), change the EA chaining mode to AREA-ARS (2) and restart the server.

     


    Article Number:

    000173875


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles