| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
secure | secure | ||
===Type=== | ===Type=== | ||
| − | + | input | |
===Synopsis=== | ===Synopsis=== | ||
How to render a hidden input field that is secure | How to render a hidden input field that is secure | ||
| ws-class-props | |||
|---|---|---|---|
| Line 1: | Line 1: | ||
{{Doc properties | {{Doc properties | ||
| − | |Subject version=2.0 | + | |Subject version=2.0,2.1 |
|Doc subject=DevOps:Doc/FlexForm | |Doc subject=DevOps:Doc/FlexForm | ||
|Doc parent=DevOps:Doc/FlexForm/1.0/input | |Doc parent=DevOps:Doc/FlexForm/1.0/input | ||
Latest revision as of 21:09, 31 March 2023
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
