...
The view templates can largely be modeled on existing views, particularly the expiring-password.vm file, which illustrates how to advance the flow forward. For reference the variables generally available to the views are:
Name / Type | Type | Description |
|---|---|---|
flowExecutionUrl | URL | The URL to redirect to in order to advance the flow |
flowRequestContext | RequestContext | Instance of Spring Web Flow's org.springframework.webflow.execution.RequestContext for the flow conversation |
flowExecutionKey | String | An encoded portion of the flowExecutionUrl representing the flow state |
profileRequestContext | Root of the IdP's request state tree | |
encoder | An encoder useful for making view content safe | |
request | Servlet request object | |
response | Servlet response object | |
environment | Environment | Instance of org.springframework.core.env.Environment object |
custom | Object | shibboleth.CustomViewContext bean optionally defined by deployer for use in views |
Replacement of Expiring Password Flow
This flow can essentially replace the original one by reversing the sense of the condition applied in that particular flow's configuration, and utilizing "expiring-password" as a map key (or just renaming the view template).
Reference
...
Beans
The following bean is expected to be defined in conf/intercept/warning-intercept-config.xml:
Bean ID | Type | Description |
|---|---|---|
shibboleth.warning.ConditionMap | Map of conditions to test, warning intervals, and view names to render |
...
Properties
The following property can be defined in any of the consumed property files (such as idp.properties):
Name | Default | Description |
|---|---|---|
idp.warning.notifyCookiePrefix | shib_idp_warn_ | Prefix of cookie(s) to use to prevent repeated viewing of the warning page(s) |