# PocketIc support for delegate identities: expiration and targets?

**URL:** <https://forum.dfinity.org/t/pocketic-support-for-delegate-identities-expiration-and-targets/25991>\
**Category:** Developers\
**Created:** [December 29, 2023, 5:11pm UTC](https://forum.dfinity.org/t/pocketic-support-for-delegate-identities-expiration-and-targets/25991 "2023-12-29T17:11:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kristofer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/kristofer/32/11135_2.png) [@kristofer](https://forum.dfinity.org/u/kristofer)\
**Post date:** [December 29, 2023, 5:11pm UTC](https://forum.dfinity.org/t/pocketic-support-for-delegate-identities-expiration-and-targets/25991/1 "2023-12-29T17:11:46Z")

</div>

I am not getting expected responses when testing [Ic-siwe](https://forum.dfinity.org/t/ic-siwe-sign-in-with-ethereum-support-libraries-for-ic/25306) locally. I am testing that expiration and delegation targets works as expected.

Issues:

- Expired delegate identities can still be used for calls
- Calls coming from invalid target canisters are accepted

I haven’t dug deep into this yet, maybe it is an error at my end, but just wanted to check, does PocketIc fully support delegate identity expirations and targets?

---

<div class="post-metadata">

**Author:** ![mraszyk](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/mraszyk/32/7945_2.png) [@mraszyk](https://forum.dfinity.org/u/mraszyk)\
**Post date:** [January 3, 2024, 9:26am UTC](https://forum.dfinity.org/t/pocketic-support-for-delegate-identities-expiration-and-targets/25991/2 "2024-01-03T09:26:40Z")

</div>

> does PocketIc fully support delegate identity expirations and targets

No, PocketIC doesn’t support identity delegations (and their targets and expiration), but they’ll be enabled as part of the next item on the PocketIC roadmap.

---

<div class="post-metadata">

**Author:** ![kristofer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/kristofer/32/11135_2.png) [@kristofer](https://forum.dfinity.org/u/kristofer)\
**Post date:** [January 3, 2024, 12:58pm UTC](https://forum.dfinity.org/t/pocketic-support-for-delegate-identities-expiration-and-targets/25991/3 "2024-01-03T12:58:40Z")

</div>

Looking forward to coming versions 😉

---

<div class="post-metadata">

**Author:** ![kristofer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/kristofer/32/11135_2.png) [@kristofer](https://forum.dfinity.org/u/kristofer)\
**Post date:** [January 11, 2024, 11:11am UTC](https://forum.dfinity.org/t/pocketic-support-for-delegate-identities-expiration-and-targets/25991/4 "2024-01-11T11:11:23Z")

</div>

Another thing I noticed, the `Result<Output, CallError>` is not returned when calling `install_canister`. It would be good to be able to catch an error where a canister is installed with the wrong init arguments. And I guess that error ends up there?

**Edit:** I learnt that you can use `#[should_panic]` in tests to catch the panic created by installing a wasm with wrong (or no) init arguments. That solves my issue.