Changes

=== Within the GC - Where the User is Associated with an Account ===

=== Within the GC - Where the User is Associated with an Account ===

If the user can log in to an account using an LoA 2 authentication, a straightforward option is to have the user log in and “click to sign”. There should be well-described consequences of the signing action so that the user is aware that she is performing a signing action. This option is already in wide use. An example from the GC is the e-signatures applied by both manager and employee as part of the Performance Management process.

If the user can log in to an account using an LoA 2 authentication, a straightforward option is to have the user log in and “click to sign”. There should be well-described consequences of the signing action so that the user is aware that she is performing a signing action. This option is already in wide use. An example from the GC is the e-signatures applied by both manager and employee as part of the Performance Management process.

=== Outside the GC - PKI-based E-Signature Solutions ===

=== Outside the GC - PKI-based E-Signature Solutions ===

=== Outside the GC - Where the User is Associated with an Account ===

=== Outside the GC - Where the User is Associated with an Account ===

As above, if the external user can log in to an account using an LoA 2 authentication, a simple approach is to have the user log in and “click to sign”. The CRA process for changing direct deposit details for income tax rebates within My Account for Individuals is an example of e-accounts associated with the public. In these cases, the LoA is largely determined by the LoA of the authentication process used for logging in to the account.This is an example of LoA 2 because the credentials used to log in to those accounts are LoA 2. You can find more details on this in the e-signature guidance.

As above, if the external user can log in to an account using an LoA 2 authentication, a simple approach is to have the user log in and “click to sign”. The CRA process for adding a child for child benefits is an example of an e-signature where a user outside the GC is associated with an account. In these cases, the LoA of the e-signature is largely determined by the LoA of the authentication process used for logging in to the account. This is an example of LoA 2 because the credentials used to log in to those accounts are LoA 2. You can find more details on this in the e-signature guidance.

 

== Level of Assurance (LoA) 3: ==

== Level of Assurance (LoA) 3: ==