Get2FaStatus

Class Description

Returns the Status of the Two Factor Auth

RPC Configuration

Rpc Name:

Plain: Get2FaStatus
Sha1: 34775a04105b732a53e64055d8808ce02074851c

Rpc Call

RPCs can be called by their plain name or their SHA1 representation.

true

Requires Context:

Context

The context providing parameter can either be a contagt-id (8-Bytes, Alphaumeric) or an integer as a building id. The context parameter name should make the choice obviouse, the type has not to be defined manually.

false

Has Named Parameters:

false

Requires WriteAccess:

WriteAccess

Only accounts that have an explicit write access to the defined context can execute this RPC, no matter if the authentication level matches or not.

false

Requires AuthenticationLevel:

Context

Authentication levels allow the SuperUser to define a by-RPC granular access configuration. If RPCs are chained in a single unified call and lenient is enabled, all allowed RPCs will be executed, while execution will fail entirely with lenient set to false.

STANDARD_USER

Requires Subbuilding Merge Strategy:

REPLACE

Cache Configuration

Response Cache

All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache and readonly.

Cache enabled:

false

Sample Request

->

[]

<-

"disabled"

RPC Configuration​

Rpc Name:​

Requires Login:​

Requires Context:​

Has Named Parameters:​

Requires WriteAccess:​

Requires AuthenticationLevel:​

Requires Subbuilding Merge Strategy:​

Cache Configuration​

Cache enabled:​

Sample Request​