bcgov / bcgov/entity

BC Services Card Login Re-verification Issues and Exploration of Alternative Authentication Methods

Open
#34,071 1 comment 0 reactions 0 assignees View on GitHub
Pay
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

#### Background

During corporation migration research sessions, several participants experienced difficulties logging into BC Registries using their BC Services Card (BCSC). In cases where participants had previously completed BCSC setup and identity verification, the login process required them to complete identity re-verification before they could access the service.

This created friction in the user journey and may present a barrier for users attempting to complete straightforward business transactions such as corporation migrations.

Considerations for next step:

#### 1. Investigate BCSC App Re-verification Triggers
Understand the circumstances that may require users to complete the identity verification process again in their BCSC app, including but not limited to:

- Expiry of previous verification or credential validity periods
- Extended periods of inactivity
- Device changes or use of a new browser
- Changes to account information
- Renewal of Services Card
- Security-related account resets
- App reinstallation or mobile device replacement
- Other authentication or risk-based triggers

Also, confirm how BC Registries account access is affected when a user:
- Completes the BCSC app verification process again, or
- Creates a new BCSC app account using the same BC Services Card.

Specifically, determine whether users retain access to their existing BC Registries account and associated data, rather than creating or being linked to a new account.

**Outcome:** Document the conditions that can cause a user to be prompted for re-verification and assess their frequency and impact on the BC Registry user experience and existing account.

#### 2. Explore Alternative Authentication Options for Low-Risk Transactions/Filings
Evaluate whether the system should support an alternative authentication method that does not require BC Services Card identity verification for low-risk or quick filing activities (e.g., corporate migration or annual report filings).

Consider:
- Email-based verification
- Creation of a limited-access user role with restricted permissions
- Impact on user experience and completion rates

**Outcome:** Determine the feasibility of introducing an alternative authentication pathway and identify potential user roles and permissions required.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by investigating the BC Services Card re-verification triggers listed in the issue and how repeat verification or account creation affects existing BC Registries access and data. Document the conditions, frequency, and user impact, then assess the feasibility of email verification or a restricted role for low-risk filings, including the required permissions.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, authorization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.