# Caller Authentication Behavior

**URL:** <https://forum.dfinity.org/t/caller-authentication-behavior/41044>\
**Category:** Developers\
**Created:** [February 10, 2025, 3:08pm UTC](https://forum.dfinity.org/t/caller-authentication-behavior/41044 "2025-02-10T15:08:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vmr](https://avatars.discourse-cdn.com/v4/letter/v/7feea3/32.png) [@vmr](https://forum.dfinity.org/u/vmr)\
**Post date:** [February 10, 2025, 3:08pm UTC](https://forum.dfinity.org/t/caller-authentication-behavior/41044/1 "2025-02-10T15:08:31Z")

</div>

I am getting an unexpected caller authentication when I call another canister’s update method from a new canister. I do not get the error when i call the other canister’s update method directly via DFX. In both cases, the caller is exactly the same (my canister is owned by the DFX principal).

- answering my own question - that is expected because the canister is a different identity than the dfx principal
