PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 10/02/2019 12:18 PM by  Joan Herzfeldt
IPA and ADFS issues
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Joan Herzfeldt
Private
Private
Veteran Member
(155 points)
Veteran Member
Posts:59


Send Message:

--
10/01/2019 3:21 PM

    We just switched to ADFS and my IPA inbasket is requesting the user to Login again in order to see the detail of the requisition/workunit. 

    The User Action node is set up with a display type of HTML and uses File Id: recsum.htm (see attached print screen).  

     Where is the connections between the user who’s already logged in and viewing their inbasket (with the general information) to see detail.

    My basic understanding is... the system is displaying the general detail then trying to go back into the system and pull the detail using the html format in the recsum.htm file.  Somewhere in that process, there is an url/port/something that is not set up correctly.

    Can someone point me in the right direction?  



    Thanks

    Joan

    Attachments
    Tags: Inbasket, IPA, ADFS, User action
    David Williams
    Private
    Private
    Veteran Member
    (3208 points)
    Veteran Member
    Posts:1080


    Send Message:

    --
    10/01/2019 4:16 PM
    Are you on premise or hosted in the cloud?
    David Williams
    Joan Herzfeldt
    Private
    Private
    Veteran Member
    (155 points)
    Veteran Member
    Posts:59


    Send Message:

    --
    10/02/2019 9:00 AM
    On Prem
    Joan Herzfeldt
    Private
    Private
    Veteran Member
    (155 points)
    Veteran Member
    Posts:59


    Send Message:

    --
    10/02/2019 12:18 PM
    So our ADFS consultant got back to us, I needed to change the InforLawson Configurantion Set to use a ssl port (1447), it was using an non-ssl port (82).
    Some additional info from our consultant: "Interestingly enough, I tested the difference between initially logging into Portal via ADFS vs. non-ADFS. If the logon to Portal is non-ADFS, then then inbasket works with the configuration set to either port 82 or port 1447. However, if the initial Portal logon is via ADFS, then the we have to use the SSL-enable non-ADFS port of 1447."
    You are not authorized to post a reply.