<- Chrome Settings Library

ParentAccessCodeConfig

Parent Access Code Configuration
Last updated October 8, 2024

This policy specifies configuration that is used to generate and verify Parent Access Code. |current_config| is always used for generating access code and should be used for validating access code only when it cannot be validated with |future_config|. |future_config| is the primary config used for validating access code. |old_configs| should be used for validating access code only when it cannot be validated with |future_config| nor |current_config|. The expected way of using this policy is to gradually rotate access code configuration. New configuration is always put into |future_config| and at the same time the existing value is moved into |current_config|. |current_config|'s previous values are moved into |old_configs| and removed after rotation cycle is finished. This policy applies only to child user. When this policy is set Parent Access Code can be verified on child user's device. When this policy is unset it is not possible to verify Parent Access Code on child user's device.

Supported On:
Platform Start End
ChromeOS 73
Example value:

{"old_configs":{"0":{"shared_secret":"sTr6jqMTJGCbLhWI5plFTQb/VsqxwX2Q","access_code_ttl":600,"clock_drift_tolerance":300}},"future_config":{"shared_secret":"KMsoIjnpvcWmiU1GHchp2blR96mNyJwS","access_code_ttl":600,"clock_drift_tolerance":300},"current_config":{"shared_secret":"oOA9nX02LdhYdOzwMsGof+QA3wUKP4YMNlk9S/W3o+w=","access_code_ttl":600,"clock_drift_tolerance":300}}

Features: