# Mosip IDA module Keys

**URL:** <https://community.mosip.io/t/mosip-ida-module-keys/375>\
**Category:** Developer\
**Tags:** keymanager\
**Created:** [March 22, 2023, 1:39pm UTC](https://community.mosip.io/t/mosip-ida-module-keys/375 "2023-03-22T13:39:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bch](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/bch/32/438_2.png) [@bch](https://community.mosip.io/u/bch)\
**Post date:** [March 22, 2023, 1:39pm UTC](https://community.mosip.io/t/mosip-ida-module-keys/375/1 "2023-03-22T13:39:08Z")

</div>

Hi,

I have a question about id-authentication keys:  
I found two database keys one for keymanager service et other for IDA service.  
Why there is two keys DB?  
Can use keymanager service keys for IDA module

---

<div class="post-metadata">

**Author:** ![gsasikumar](https://avatars.discourse-cdn.com/v4/letter/g/b782af/32.png) [@gsasikumar](https://community.mosip.io/u/gsasikumar)\
**Post date:** [March 24, 2023, 5:07am UTC](https://community.mosip.io/t/mosip-ida-module-keys/375/2 "2023-03-24T05:07:51Z")

</div>

`id-authentication` is designed to be independent, the design allows independent verifiers against the issuer. So if we think of the government as an Issuer, we can have multiple verifiers to host this verified data and provide verification service.

When we have multiple verifiers we want to provide a simple ready-to-use with all embedded service. That’s why you would see the `keymanager` embedded here.

---

<div class="post-metadata">

**Author:** ![bch](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/bch/32/438_2.png) [@bch](https://community.mosip.io/u/bch)\
**Post date:** [March 24, 2023, 6:04am UTC](https://community.mosip.io/t/mosip-ida-module-keys/375/3 "2023-03-24T06:04:06Z")

</div>

Thank you @gsasikumar for your reply, it’s very clear now