Problem Statement (Mandatory)
The current IDA architecture has separate services for authentication and OTP processing, along with an internal-authentication-service that introduces additional service and deployment complexity. IDA also has a dependency on WEBS for receiving or propagating identity-related updates.
This architecture increases the number of services that need to be deployed, maintained, monitored and scaled. It also introduces additional dependencies in the identity update flow, where changes made in the ID Repository are not directly and actively propagated to IDA.
The authentication and OTP capabilities should be consolidated within the IDA authentication-service, the internal-authentication-service should be removed, and the dependency on WEBS should be eliminated. IDA should instead support an active update mechanism through which changes from the ID Repository are propagated to IDA.
Purpose (Mandatory)
The change is required to:
Reduce the number of services and deployment components in IDA.
Simplify the authentication architecture by consolidating OTP functionality into authentication-service.
Remove the need for internal-authentication-service.
Eliminate the dependency on WEBS for identity updates to IDA.
Enable ID Repository to actively notify/update IDA when relevant identity data changes.
Improve maintainability and reduce operational overhead.
Ensure IDA continues to provide authentication functionality without requiring changes to its consumers.
Problem Statement (Mandatory)
The current IDA architecture has separate services for authentication and OTP processing, along with an internal-authentication-service that introduces additional service and deployment complexity. IDA also has a dependency on WEBS for receiving or propagating identity-related updates.
This architecture increases the number of services that need to be deployed, maintained, monitored and scaled. It also introduces additional dependencies in the identity update flow, where changes made in the ID Repository are not directly and actively propagated to IDA.
The authentication and OTP capabilities should be consolidated within the IDA authentication-service, the internal-authentication-service should be removed, and the dependency on WEBS should be eliminated. IDA should instead support an active update mechanism through which changes from the ID Repository are propagated to IDA.
Purpose (Mandatory)
The change is required to:
Reduce the number of services and deployment components in IDA.
Simplify the authentication architecture by consolidating OTP functionality into authentication-service.
Remove the need for internal-authentication-service.
Eliminate the dependency on WEBS for identity updates to IDA.
Enable ID Repository to actively notify/update IDA when relevant identity data changes.
Improve maintainability and reduce operational overhead.
Ensure IDA continues to provide authentication functionality without requiring changes to its consumers.