IBM Verify

IBM Verify

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Changing Login Page

    Posted Thu October 29, 2020 03:31 PM
    Edited by Joao Goncalves Thu October 29, 2020 03:51 PM
    After customizing the default login page for a reverse proxy under management/C/login_success.html, these changes worked fine.

    Then I wanted to change to login_success.html, and added a new one file named, login_success.json, with a json content.
    After this I went to the reverse proxy configuration file, and changed the login entry to:

    # Page displayed after successful login
    login-success = login_success.json

    I deployed the changes, restarted the Reverse proxy, but the system still returns the html file, and not the json file.
    I went to the log files, and validated the config_data_*.log. It is using the json file!

    What am I missing?

    I noticed that the parameter default-response-type is set to text/html, and I am trying to send a json file.
    If this is the problem, how can I simulate a restAPI in response to pkmslogin.form?

    If I have to change the default-response-type and set it for application/json to be used exclusively for this login page?

    From what I managed to find, ISAM restAPI, are only for ISAM management support!

    ------------------------------
    Joao Goncalves
    Pyxis, Lda.
    Sintra
    +351 91 721 4994
    ------------------------------


  • 2.  RE: Changing Login Page

    Posted Thu October 29, 2020 04:09 PM
    Joao,
     
    WebSEAL uses the 'accept' HTTP header to determine the type of response to return.  Changing the login-success configuration entry to login.json will have no impact.  If you want to change the default response type from html to json you need to use the default-response-type configuration entry.
     
    I hope that this helps.
     
     

    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor
    Phone: 61-7-5552-4008
    E-mail: scotte@au1.ibm.com
    1 Corporate Court
    Bundall, QLD 4217
    Australia
     
     



    Original Message


  • 3.  RE: Changing Login Page

    Posted Thu October 29, 2020 04:35 PM
    I worked fine.
    But is there any way I can create an ISAM restAPI to handle logins? Instead of using pkmslogin.form, could I create a new junction /auth_jct/ that answer to restAPI for login, logout, etc, where I can send json file with the user credentials and so on?

    ------------------------------
    Joao Goncalves
    Pyxis, Lda.
    Sintra
    +351 91 721 4994
    ------------------------------

    Original Message


  • 4.  RE: Changing Login Page

    Posted Thu October 29, 2020 04:41 PM
    Joao,
     
    WebSEAL will only natively accept a POST from a login form.  If you want to perform a username/password login using REST you will need to implement your own EAI.
     
    Thanks.
     
     

    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor
    Phone: 61-7-5552-4008
    E-mail: scotte@au1.ibm.com
    1 Corporate Court
    Bundall, QLD 4217
    Australia
     
     



    Original Message


  • 5.  RE: Changing Login Page

    Posted Fri October 30, 2020 03:27 AM
    Hello Joao,

    What you want sounds a lot like an authentication policy, which is in fact an EAI hosted on the ISAM runtime. You can definitely do a login this way, and most likely also a logout. I have never implemented a logout using a policy yet. But I know there is an eai response header to do a logout. You would have to check if the policy can use this response header or if you have to invalidate the credential by overwriting it.

    ------------------------------
    Laurent LA Asselborn
    ------------------------------

    Original Message


Related Content