m (E00a555c-1e5d-4eb3-b26b-5be8dc16c657 moved page DevOps:Doc/FlexForm/1.0.0/input/secure to input/secure without leaving a redirect: Text replacement - "1.0.0" to "1.0") |
|||
| ws-page-props | |||
|---|---|---|---|
| Line 1: | Line 1: | ||
{{Doc properties | {{Doc properties | ||
|Doc subject=DevOps:Doc/FlexForm | |Doc subject=DevOps:Doc/FlexForm | ||
| − | |Doc parent=DevOps:Doc/FlexForm/1 | + | |Subject version=1.0.0 |
| + | |Doc parent=DevOps:Doc/FlexForm/1.0/input | ||
|Doc sort order=110 | |Doc sort order=110 | ||
|Doc target group=User | |Doc target group=User | ||
| − | |||
}} | }} | ||
Revision as of 16:28, 7 April 2022
Name
secure
Type
_input
Synopsis
How to render a hidden input field that is secure
Description
_input elements of type secure are similar to type hidden. The difference is that a secure field is not readable by a user and a form will fail if it gets altered using Browsers developer tools
Parameters
type="secure"
All other valid parameters for an input field are valid
Example
<_input type="secure" name="token" value="123231321" />
This will render something similar to
<input name="2425fb14579653aef53179a2849e4593ES5rgMk=" value="7cade404c7d02c02a3087e4fd6954caby0QljHbAPys0" type="hidden">
Note
When using action="get" a secure field will not be returned in the url
