AclTokenType
AllowForwardHeaders
Name |
Description |
No parsing shall be performed. |
|
Only process the standard |
|
Only process the non standard but widely used These headers are not official standards but widely used. Users are advised to avoid them for new applications. |
|
Will process both and . Be aware that mixing the 2 headers can open security holes has specially crafted requests that are not validated as proxy level can allow bypassing the proxy desired forward value. For example, a proxy will add the |
ApolloWSMessageType
Attestation
AuthenticatorAttachment
AuthenticatorTransport
BridgeEventType
Name |
Description |
This event will occur when a new SockJS socket is created. |
|
This event will occur when a SockJS socket is closed. |
|
This event will occur when SockJS socket is on idle for longer period of time than configured. |
|
This event will occur when the last ping timestamp is updated for the SockJS socket. |
|
This event will occur when a message is attempted to be sent from the client to the server. |
|
This event will occur when a message is attempted to be published from the client to the server. |
|
This event will occur when a message is attempted to be delivered from the server to the client. |
|
This event will occur when a client attempts to register a handler. |
|
This event will occur when a client successfully registered. The raw message used for registration, notified with event |
|
This event will occur when a client attempts to unregister a handler. |
CircuitBreakerState
Name |
Description |
The |
|
The |
|
The |
ClientAuth
Name |
Description |
No client authentication is requested or required. |
|
Accept authentication if presented by client. If this option is set and the client chooses not to provide authentication information about itself, the negotiations will continue. |
|
Require client to present authentication, if not presented then negotiations will be declined. |
ContainerSerializationStyle
Name |
Description |
Comma separated values: "value1,value2,value3" aliases: "csv", "commaDelimited", "form", "simple" |
|
Space separated values: "value1 value2 value3" aliases: "ssv", "spaceDelimited" |
|
+ Pipe separated values: "value1 |
|
value2 |
value3" aliases: "psv", "pipeDelimited" + |
Dot delimited values: "value1.value2.value3" aliases: "dsv", "dotDelimited", "label" |
|
For internal usage, don't use it |
|
For internal usage, don't use it |
CookieSameSite
Name |
Description |
The browser will send cookies with both cross-site requests and same-site requests. |
|
The browser will only send cookies for same-site requests (requests originating from the site that set the cookie). If the request originated from a different URL than the URL of the current location, none of the cookies tagged with the Strict attribute will be included. |
|
Same-site cookies are withheld on cross-site subrequests, such as calls to load images or frames, but will be sent when a user navigates to the URL from an external site; for example, by following a link. |
DKIMSignAlgorithm
DnsResponseCode
Name |
Description |
ID 0, no error |
|
ID 1, format error |
|
ID 2, server failure |
|
ID 3, name error |
|
ID 4, not implemented |
|
ID 5, operation refused |
|
ID 6, domain name should not exist |
|
ID 7, resource record set should not exist |
|
ID 8, rrset does not exist |
|
ID 9, not authoritative for zone |
|
ID 10, name not in zone |
|
ID 11, bad extension mechanism for version |
|
ID 12, bad signature |
|
ID 13, bad key |
|
ID 14, bad timestamp |
ExecStatus
HashAlgorithm
HashSaltStyle
HttpVersion
JsonEventType
Label
Name |
Description |
Local address in client-host or host-client connections (used in net, http and datagram domains) |
|
Remote address in client-host or host-client connections (used in net and http domains) |
|
Path of the URI for client or server requests (used in http domain) |
|
Route as provided by routing modules to the http requests |
|
Method (GET, POST, PUT, etc.) of an HTTP requests (used in http domain) |
|
HTTP response code (used in http domain) |
|
Class name. When used in error counters (in net, http, datagram and eventbus domains) it relates to an exception that occurred. When used in verticle domain, it relates to the verticle class name. |
|
Event bus address |
|
Event bus side of the metric, it can be either "local" or "remote" |
|
Event bus failure name from a ReplyFailure object |
|
Pool type, such as "worker" or "datasource" (used in pools domain) |
|
Pool name (used in pools domain) |
|
Client namespace |
LoggerFormat
Name |
Description |
remote-client - - [timestamp] "method uri version" status content-length "referrer" "user-agent" |
|
remote-client - method uri version status content-length duration ms |
|
method uri status - content-length duration |
|
Will use user defined formatter function. |
LoginOption
either DISABLED, OPTIONAL, REQUIRED or XOAUTH2
DISABLED means no login will be attempted
NONE means a login will be attempted if the server supports in and login credentials are set
REQUIRED means that a login will be attempted if the server supports it and the send operation will fail otherwise
XOAUTH2 means that a login will be attempted using Google Gmail Oauth2 tokens
Name |
Description |
- |
|
- |
|
- |
|
- |
MetricsDomain
Name |
Description |
Net server metrics. |
|
Net client metrics. |
|
Http server metrics. |
|
Http client metrics. |
|
Datagram socket metrics. |
|
Event bus metrics. |
|
Named pools metrics. |
|
Verticle metrics. |
MySQLSetOption
OAuth2FlowType
Name |
Description |
The authorization code is obtained by using an authorization server as an intermediary between the client and resource owner. Instead of requesting authorization directly from the resource owner, the client directs the resource owner to an authorization server (via its user-agent as defined in [RFC2616]), which in turn directs the resource owner back to the client with the authorization code. Before directing the resource owner back to the client with the authorization code, the authorization server authenticates the resource owner and obtains authorization. Because the resource owner only authenticates with the authorization server, the resource owner's credentials are never shared with the client. The authorization code provides a few important security benefits, such as the ability to authenticate the client, as well as the transmission of the access token directly to the client without passing it through the resource owner's user-agent and potentially exposing it to others, including the resource owner. |
|
The implicit grant is a simplified authorization code flow optimized for clients implemented in a browser using a scripting language such as JavaScript. In the implicit flow, instead of issuing the client an authorization code, the client is issued an access token directly (as the result of the resource owner authorization). The grant type is implicit, as no intermediate credentials (such as an authorization code) are issued (and later used to obtain an access token). When issuing an access token during the implicit grant flow, the authorization server does not authenticate the client. In some cases, the client identity can be verified via the redirection URI used to deliver the access token to the client. The access token may be exposed to the resource owner or other applications with access to the resource owner's user-agent. Implicit grants improve the responsiveness and efficiency of some clients (such as a client implemented as an in-browser application), since it reduces the number of round trips required to obtain an access token. However, this convenience should be weighed against the security implications of using implicit grants, especially when the authorization code grant type is available. |
|
The resource owner password credentials (i.e., username and password) can be used directly as an authorization grant to obtain an access token. The credentials should only be used when there is a high degree of trust between the resource owner and the client (e.g., the client is part of the device operating system or a highly privileged application), and when other authorization grant types are not available (such as an authorization code). Even though this grant type requires direct client access to the resource owner credentials, the resource owner credentials are used for a single request and are exchanged for an access token. This grant type can eliminate the need for the client to store the resource owner credentials for future use, by exchanging the credentials with a long-lived access token or refresh token. |
|
The client credentials (or other forms of client authentication) can be used as an authorization grant when the authorization scope is limited to the protected resources under the control of the client, or to protected resources previously arranged with the authorization server. Client credentials are used as an authorization grant typically when the client is acting on its own behalf (the client is also the resource owner) or is requesting access to protected resources based on an authorization previously arranged with the authorization server. |
|
RFC7523 |
ParameterLocation
ParameterType
Name |
Description |
STRING Type accept every string |
|
- |
|
- |
|
It allows true, false, t, f, 1, 0 |
|
INT type does the validation with Integer.parseInt(value) |
|
FLOAT type does the validation with Float.parseFloat(value) |
|
DOUBLE type does the validation with Double.parseDouble(value) |
|
DATE as defined by full-date - RFC3339 |
|
DATETIME as defined by date-time - RFC3339 |
|
TIME as defined by partial-time - RFC3339 |
|
- |
|
- |
|
- |
|
- |
|
UUID as defined by RFC4122 |
ProxyType
PublicKeyCredential
RedisClientType
Name |
Description |
The client should work in single server mode (the default). |
|
The client should work in sentinel mode. When this mode is active use the link to define which role to get the client connection to. |
|
The client should work in cluster mode. When this mode is active use the link to define when replica nodes can be used for read only queries. |
RedisReplicas
RedisRole
ReplyFailure
Name |
Description |
The message send failed because no reply was received before the timeout time. |
|
The message send failed because no handlers were available to handle the message. |
|
The message send failed because the recipient actively sent back a failure (rejected the message). |
|
A fatal error occured while delivering the message. Do not retry to send. |
ResponseType
Name |
Description |
C String simple String. |
|
C String simple String representing an error. |
|
boolean value. |
|
numeric value. |
|
byte array value. |
|
Push message |
|
Attribute message |
|
List of multiple bulk responses (List, Set, Map). |
ResultSetConcurrency
ResultSetType
SessionBehavior
If the release behavior is being used, any of the locks held in association with the session are released, and the ModifyIndex of the key is incremented. Alternatively, if the delete behavior is used, the key corresponding to any of the held locks is simply deleted. This can be used to create ephemeral entries that are automatically deleted by Consul.
Name |
Description |
- |
|
- |
ShiroAuthRealmType
SslMode
Name |
Description |
establish an unencrypted connection. |
|
establish an encrypted connection if the server supports encrypted connections, falling back to an unencrypted connection if an encrypted connection cannot be established. |
|
establish an encrypted connection if the server supports encrypted connections. The connection attempt fails if an encrypted connection cannot be established. |
|
Like REQUIRED, but additionally verify the server Certificate Authority (CA) certificate against the configured CA certificates. The connection attempt fails if no valid matching CA certificates are found. |
|
Like VERIFY_CA, but additionally perform host name identity verification by checking the host name the client uses for connecting to the server against the identity in the certificate that the server sends to the client. |
SslMode
Name |
Description |
only try a non-SSL connection. |
|
first try a non-SSL connection; if that fails, try an SSL connection. |
|
first try an SSL connection; if that fails, try a non-SSL connection. |
|
only try an SSL connection. If a root CA file is present, verify the certificate in the same way as if verify-ca was specified. |
|
only try an SSL connection, and verify that the server certificate is issued by a trusted certificate authority (CA). |
|
only try an SSL connection, verify that the server certificate is issued by a trusted CA and that the requested server host name matches that in the certificate. |
StartTLSOptions
either DISABLED, OPTIONAL or REQUIRED
DISABLED means STARTTLS will not be used in any case
OPTIONS means STARTTLS will be used if the server supports it and a plain connection will be used otherwise please note that this option is not a secure as it seems since a MITM attacker can remove the STARTTLS line from the capabilities reply.
REQUIRED means that STARTTLS will be used if the server supports it and the send operation will fail otherwise
Name |
Description |
- |
|
- |
|
- |
Status
TransactionIsolation
Name |
Description |
Implements dirty read, or isolation level 0 locking, which means that no shared locks are issued and no exclusive locks are honored. When this option is set, it is possible to read uncommitted or dirty data; values in the data can be changed and rows can appear or disappear in the data set before the end of the transaction. This is the least restrictive of the four isolation levels. |
|
Specifies that shared locks are held while the data is being read to avoid dirty reads, but the data can be changed before the end of the transaction, resulting in nonrepeatable reads or phantom data. |
|
Locks are placed on all data that is used in a query, preventing other users from updating the data, but new phantom rows can be inserted into the data set by another user and are included in later reads in the current transaction. Because concurrency is lower than the default isolation level, use this option only when necessary. |
|
Places a range lock on the data set, preventing other users from updating or inserting rows into the data set until the transaction is complete. This is the most restrictive of the four isolation levels. Because concurrency is lower, use this option only when necessary. |
|
For engines that support it, none isolation means that each statement would essentially be its own transaction. |
Transport
Name |
Description |
Slow and old fashioned JSONP polling. This transport will show "busy indicator" (aka: "spinning wheel") when sending data. |
|
Long-polling using cross domain XHR |
TxnKVVerb
Name |
Description |
Sets the Key to the given Value |
|
Sets the Key to the given Value with check-and-set semantics. The Key will only be set if its current modify index matches the supplied Index |
|
Locks the Key with the given Session. The Key will only obtain the lock if the Session is valid, and no other session has it locked |
|
Unlocks the Key with the given Session. The Key will only release the lock if the Session is valid and currently has it locked |
|
Gets the Key during the transaction. This fails the transaction if the Key doesn't exist. The key may not be present in the results if ACLs do not permit it to be read |
|
Gets all keys with a prefix of Key during the transaction. This does not fail the transaction if the Key doesn't exist. Not all keys may be present in the results if ACLs do not permit them to be read |
|
Fails the transaction if Key does not have a modify index equal to Index |
|
Fails the transaction if Key is not currently locked by Session |
|
Deletes the Key |
|
Deletes all keys with a prefix ofKey |
|
Deletes the Key with check-and-set semantics. The Key will only be deleted if its current modify index matches the supplied Index |