Version Affected: All
Overview
A Form Post Begin Site (FormPost.aspx) lets an IdP realm accept the username and mode (Public or Private), plus optionally a password and/or shared secret, as variables submitted by a Forms POST from another website or external page, instead of the user typing those details directly into the realm. Once the Forms POST is accepted, the user proceeds through the usual workflow.
Configure the Begin Site
- Configure the Begin Site following the Form Post Begin Site Configuration Guide.
- If both the username and password are supplied via the Forms POST, change the workflow (on the Workflow tab) to accept username and password on the same page. If only the password is expected, adjust the workflow accordingly.
Test the Begin Site
- Create a simple HTML file with a form that POSTs to the Begin Site, for example:
<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="utf-8" />
<title></title>
</head>
<body>
<form id="myform" method="post" action="https://idp.domain.com/Secureauth53/Formpost.aspx">
<label for="UserID">User ID:</label><input name="UserID" value="user1" />
<label for="Password">Password:</label><input name="Password" value="P@$$w0rd" />
<label for="Mode">Mode:</label><input name="Mode" value="Public" />
<label for="SharedSecret">SharedSecret:</label><input name="SharedSecret" value="111" />
<button type="submit">Submit</button>
</form>
</body>
</html>- Edit the form's action attribute to point to the realm's actual Begin Site URL. This file does not need to be placed on the IdP -- it can be saved and opened from any machine, such as a workstation.
- Open the file in a browser by double-clicking it. Change the User ID, Password, Mode, and SharedSecret field values if needed.
- Click Submit to test.
- If successful, the user proceeds through the workflow, and the audit log shows an entry similar to:
The current identity from Form Post: user1
Special Considerations
If the username or password submitted is incorrect, the Begin Site does not fail cleanly -- the user is left on a blank screen with no error message or indication of a problem.
If any of the expected variables are missing entirely (not just blank, but undefined), the Begin Site generates:
Error: Object reference not set to an instance of an objectThis can happen when a user browses directly to the realm (for example, SecureAuth.aspx), which redirects to the Begin Site without a Forms POST ever having been made.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.