# Enable keychain?

**URL:** <https://community.appmysite.com/t/enable-keychain/445>\
**Category:** Download\
**Created:** [July 19, 2022, 9:54am UTC](https://community.appmysite.com/t/enable-keychain/445 "2022-07-19T09:54:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![BUSAYO](https://sea2.discourse-cdn.com/flex016/user_avatar/community.appmysite.com/busayo/32/837_2.png) [@BUSAYO](https://community.appmysite.com/u/BUSAYO)\
**Post date:** [July 19, 2022, 9:54am UTC](https://community.appmysite.com/t/enable-keychain/445/1 "2022-07-19T09:54:17Z")

</div>

I am trying to rebuild my app and enable keychain but it won’t work due to the below.

By default the uploaded iPhone Provisioning Profile does not include the “Associated Domains” and “AutoFill Credential Provider” permissions. You will need to regenerate your iPhone Provisioning Profile after adding these permissions.

Please where can I find the guide to re-configuring with the above in mind?

---

<div class="post-metadata">

**Author:** ![barroshill](https://avatars.discourse-cdn.com/v4/letter/b/90ced4/32.png) [@barroshill](https://community.appmysite.com/u/barroshill)\
**Post date:** [July 27, 2022, 12:44pm UTC](https://community.appmysite.com/t/enable-keychain/445/2 "2022-07-27T12:44:04Z")

</div>

I think you need to reconfigure your App Identifier and add permissions for Associated Domains and AutoFill Credential Provider. Read the bullet points in this article: [Step 1: App Identifier - AppMySite](https://www.appmysite.com/support/app-identifier/)

I would also recommend contacting support as they would be able to pinpoint the exact issue.

---

<div class="post-metadata">

**Author:** ![Nancy\_AppMySite](https://sea2.discourse-cdn.com/flex016/user_avatar/community.appmysite.com/nancy_appmysite/32/2219_2.png) [@Nancy\_AppMySite](https://community.appmysite.com/u/Nancy_AppMySite)\
**Post date:** [March 20, 2024, 9:39am UTC](https://community.appmysite.com/t/enable-keychain/445/3 "2024-03-20T09:39:28Z")

</div>

Hi @BUSAYO,

Has this issue been addressed?
