Applies To:Show Versions
- 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.0
Setting a URL or SPA view to be a login page
- On the Main tab, click.The Anti-Fraud Profiles screen opens.
- From the list of profiles, select the relevant profile.The Anti-Fraud Profile Properties screen opens.
- In the Anti-Fraud Configuration area, clickURL List.The URL List opens.
- Click the URL or view that you want to set as the login page, or clickAdd URL(orAdd View) if you want to create a new URL or view to be a login page.
- In the URL Configuration (or View Configuration) area, selectParameters.The Parameters list is displayed.
- Click theAddbutton.The Parameter Settings screen opens.
- In theParameter Namefield, choose one of the following types for the parameter name:
- Explicit: Assign a specific parameter name.
- Wildcard: Assign a wildcard expression for the parameter name. Any parameter name that matches the wildcard expression is considered legal and receives protection. For example, typing the wildcard expression*specifies that any parameter name is allowed.
- If you choseExplicit, type the parameter name.
- If you choseWildcard, type the wildcard expression.The syntax for wildcard entities is based on shell-style wildcard characters. This following table lists the wildcard characters that you can use so that the entity name matches multiple objects.Wildcard characterMatches*All characters?Any single character[abcde]Exactly one of the characters listed[!abcde]Any character not listed[a-e]Exactly one character in the range[!a-e]Any character not in the rangeIf a wildcard character is actually used as part of a parameter name and you don't want it to be treated as a wildcard character, use\and then the character to indicate that it should not be used as a wildcard character.A regular expression should not be used as part of the wildcard expression for a parameter name.
- SelectIdentify as Username.Only one parameter per URL can have the attributeIdentify as Username.
- ClickCreateand thenBack to URL(orBack to View).
- Under URL Configuration (or View Configuration) selectLogin Page Properties.Configuring theLogin Page Propertiesis not required but recommended because a login cannot be verified as successful unless at least one of the criteria in theLogin Page Propertiesis configured.
- For theURL is Login Pagesetting, select theYescheck box.The Login Page Properties appear.IfURL is Login Pageis enabled, you must configure at least one of the Login Page Properties. If you configure more than one Login Page Property, then all the criteria for all properties must be fulfilled for the BIG-IP system to consider the login successful.
- In theA string that should appear in the response bodyfield, type a string that should appear in the successful response to the login URL.
- In theA string that should NOT appear in the response bodyfield, type a string that should not appear in the successful response to the login URL.
- In theExpected HTTP response status codefield, selectSpecifyand type the HTTP response status code that the server must return to the user upon successful login, or selectNone.If you selectNone, HTTP response code is not used to determine a successful login.
- In theExpected response headerfield, type a header name that the successful response to the login URL must match.
- In theExpected cookie namefield, type a cookie name that the successful response to the login URL must include.
- ClickSave.The Login Page and Parameter settings are saved.