SecretStorageStatus
Defined in: src/crypto-api/index.ts:1185
The result of a call to CryptoApi.getSecretStorageStatus.
Properties
Section titled “Properties”defaultKeyId
Section titled “defaultKeyId”defaultKeyId:
string|null
Defined in: src/crypto-api/index.ts:1190
The ID of the current default secret storage key.
ready:
boolean
Defined in: src/crypto-api/index.ts:1187
Whether secret storage is fully populated. The same as CryptoApi.isSecretStorageReady.
secretStorageKeyValidityMap
Section titled “secretStorageKeyValidityMap”secretStorageKeyValidityMap:
object
Defined in: src/crypto-api/index.ts:1201
For each secret that we checked whether it is correctly stored in secret storage with the default secret storage key.
Note that we will only check that the key backup key is stored if key backup is currently enabled (i.e. that
CryptoApi.getActiveSessionBackupVersion returns non-null). m.megolm_backup.v1 will only be present in that case.
(This is an object rather than a Map so that it JSON.stringify()s nicely, since its main purpose is to end up
in logs.)
m.cross_signing.master?
Section titled “m.cross_signing.master?”
optionalm.cross_signing.master?:boolean
m.cross_signing.self_signing?
Section titled “m.cross_signing.self_signing?”
optionalm.cross_signing.self_signing?:boolean
m.cross_signing.user_signing?
Section titled “m.cross_signing.user_signing?”
optionalm.cross_signing.user_signing?:boolean
m.megolm_backup.v1?
Section titled “m.megolm_backup.v1?”
optionalm.megolm_backup.v1?:boolean
org.matrix.msc3814?
Section titled “org.matrix.msc3814?”
optionalorg.matrix.msc3814?:boolean