Create login towards a basic website

Create a modForms module — this is the module that handles the Access Gateway Web based logins.

The guide assumes that a valid certificate is already in place.

How to create a modForms module

  1. Open the Access Gateway Admin GUI.

  2. On the left hand side, right-click Modules.
    menu

  3. Choose Add module
    This will start a wizard that will guide you through the next steps.

  4. In the wizard: Click Next and then click Authentication and Form-Based Authentication.

    The name that is requested is a "Friendly Name" for the module itself. Recommended to set a name that explains that this module is for this website. This will make the configuration more understandable later on if changes are to be done.

  1. After the name has been set, scroll to the Authentication Methods.
    Add the authentication method you want to use.

    If you want to use a specific authentication method for this Listener, you need to create the authentication method in the Pointsharp ID Server Admin.
    Using a specific authentication method with a name that explains what it is used for, will help troubleshooting as well, since that authentication method name will be displayed in the logs in the Admin Portal.
    You can also use multiple authentication methods for a modForms module.Then there will be a drop-down list on the login page that displays all the methods that are available for use.

  1. Continue the Wizard and complete it with Apply. The modForms module is now created and ready to be used. Next step is to create a Listener that the modForms module will be added to.

Form-based Authentication configuration

See Form-based Authentication configuration.

Create Listener

The guide assumes that a valid certificate and a modForms module are already in place.

  1. Open the Access Gateway Admin GUI.

  2. On the left hand side, right-click IIS Listeners.
    menu

  3. Choose Add Listeners
    This will start a wizard that will guide you through the next steps.

  4. Set the Address. This is the external DNS name to be used for this Listener in the Access Gateway.
    Add new listener configuration wizard

  5. Scroll down to the Rules section, click Add.

  6. Next page contains several options. These listed below are needed for this specific scenario. Please click in the ? in the top right corner for explanations of all values, this guide does not use them all for a basic website.
    listener add2

    Name: A friendly name, for example, if it is an intranet site.

    Path: The path that this rule is valid for. In this example we add /intranet.

    HTTP Host Header: Not used in this example, the From Request is unchecked.

    Keeping it unchecked is needed, since we have an external DNS that is named, for example, https://intranet.company.com, but the internal resource uses another path that is https://test.company.local.
    The path towards the back-end Server will be https://intranet.company.local/intranet when From Request is disabled. If enabled, the path would be https://intranet.company.com/intranet.

    Back-end Server URL: The path towards the Server to which the Access Gateway should proxy the traffic.

  7. Scroll down to Module Configuration Names and add the modForms module created at the beginning of this guide.

  8. Apply the correct modForms and finish the Wizard.

  9. You should now be able to see a new Listener, added with a rule for the intranet site using the Access Gateway’s login page with the authentication method (or methods) that was configured.

  10. Save and Publish to complete the configuration.