Updates a gate
Path Parameters
ID of the gate
36
Body
Request body to update an existing gate. This will not affect whether a gate is enabled or not.
Human-readable name of the gate. This should be something helpful to organize gates.
scope
, siteAccess
, block
String for the resulting scope of the gate. If the rules of the gate apply to the user being verified, then this scope will be surfaced in the JWT
The rules which will be used to evaluate users being verified. If multiple rules are present in a single gate, then all the rules need to apply for the user to gain the scope defined by the gate.
Response
36
Human-readable name of the gate. This should be something helpful to organize gates.
The rules which will be used to evaluate users being verified. If multiple rules are present in a single gate, then all the rules need to apply for the user to gain the scope defined by the gate.
scope
, siteAccess
, block
String for the resulting scope of the gate. If the rules of the gate apply to the user being verified, then this scope will be surfaced in the JWT. If a scope is not provided for the gate, the default behavior of the gate would be to block access to users that the rules do not currently apply to.
If the gate is enabled, then this timestamp will be present.
Was this page helpful?