# Proposal: Implementing Blocklisted Words Validation for Android Registration Client (Issue #644)

**URL:** <https://community.mosip.io/t/proposal-implementing-blocklisted-words-validation-for-android-registration-client-issue-644/2611>\
**Category:** Android Registration Client\
**Tags:** android, regclient\
**Created:** [March 28, 2026, 7:36am UTC](https://community.mosip.io/t/proposal-implementing-blocklisted-words-validation-for-android-registration-client-issue-644/2611 "2026-03-28T07:36:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abdul\_Raheem](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/abdul_raheem/32/1987_2.png) [@Abdul\_Raheem](https://community.mosip.io/u/Abdul_Raheem)\
**Post date:** [March 28, 2026, 7:36am UTC](https://community.mosip.io/t/proposal-implementing-blocklisted-words-validation-for-android-registration-client-issue-644/2611/1 "2026-03-28T07:36:45Z")

</div>

**Hello Team MOSIP,**

I am interested in contributing to the Android Registration Client by implementing **Blocklisted Words Validation** as described in [GitHub Issue #644](https://github.com/mosip/android-registration-client/issues/644).

I have reviewed the requirement for preventing prohibited words in demographic fields, the acknowledgement page, and the packet approval stage. Before I dive into the implementation, I want to ensure my technical approach aligns with the current architecture:

1. **Configuration:** Does a global config key for prohibited words already exist in the MOSIP Kernel that the Android Client should sync with, or should I introduce a new local config?

2. **Validation Logic:** I plan to build a `BlocklistValidator` utility (Dart/Flutter). Are there specific MOSIP-standard regex patterns or libraries I should use for multilingual/Unicode-safe matching?

3. **Auditing:** Which existing audit service class is recommended for logging “Blocklist Violation” attempts on the Android client?

I’ve previously shared some initial thoughts on the [GitHub issue](https://github.com/mosip/android-registration-client/issues/644), but I wanted to reach out here to ensure my proposed design aligns perfectly with MOSIP’s architectural roadmap and best practices.

Thank you for your time!

Best regards,  
Abdul Raheem  
GitHub: abd-RAHEEM

---

<div class="post-metadata">

**Author:** ![pragya2709](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@pragya2709](https://community.mosip.io/u/pragya2709)\
**Post date:** [March 31, 2026, 6:52am UTC](https://community.mosip.io/t/proposal-implementing-blocklisted-words-validation-for-android-registration-client-issue-644/2611/2 "2026-03-31T06:52:37Z")

</div>

> [@Abdul\_Raheem](#):
>
> I am interested in contributing to the Android Registration Client by implementing **Blocklisted Words Validation** as described in [GitHub Issue #644](https://github.com/mosip/android-registration-client/issues/644).
> 
> I have reviewed the requirement for preventing prohibited words in demographic fields, the acknowledgement page, and the packet approval stage. Before I dive into the implementation, I want to ensure my technical approach aligns with the current architecture:
> 
> 1. **Configuration:** Does a global config key for prohibited words already exist in the MOSIP Kernel that the Android Client should sync with, or should I introduce a new local config?
> 2. **Validation Logic:** I plan to build a `BlocklistValidator` utility (Dart/Flutter). Are there specific MOSIP-standard regex patterns or libraries I should use for multilingual/Unicode-safe matching?
> 3. **Auditing:** Which existing audit service class is recommended for logging “Blocklist Violation” attempts on the Android client?
> 
> I’ve previously shared some initial thoughts on the [GitHub issue](https://github.com/mosip/android-registration-client/issues/644), but I wanted to reach out here to ensure my proposed design aligns perfectly with MOSIP’s architectural roadmap and best practices.
> 
> Thank you for your time!

Hi @Abdul_Raheem

Thank you for your detailed proposal and for taking the time to think through the implementation approach so thoroughly.

We are currently reviewing your proposed design to ensure it aligns with the existing MOSIP architecture and best practices. We appreciate the considerations you’ve raised around configuration, validation logic, and auditing. They’re all very relevant to the solution.

We’ll get back to you shortly with feedback and any recommendations or clarifications to help you proceed.

Thanks again for your interest in contributing!

Warm Regards,  
Pragya  
Product Owner  
Android Registration Client