# Identity between canister owner and function caller are not equal **URL:** \ **Category:** Language Support\ **Tags:** Motoko\ **Created:** [June 6, 2021, 11:19am UTC](https://forum.dfinity.org/t/identity-between-canister-owner-and-function-caller-are-not-equal/4874 "2021-06-06T11:19:50Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![cryptoschindler](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/cryptoschindler/32/26_2.png) [@cryptoschindler](https://forum.dfinity.org/u/cryptoschindler)\ **Post date:** [June 6, 2021, 1:10pm UTC](https://forum.dfinity.org/t/identity-between-canister-owner-and-function-caller-are-not-equal/4874/2 "2021-06-06T13:10:21Z")
Hey, I’m not sure if `dfx --identity default deploy` stops the proxying through the wallet canister. I’m not on a machine right now but maybe you can check the `dfx deploy --help` command to see if there’s a flag for it? This is for reference: > [@Dfx 0.7.1 released with breaking changes](https://forum.dfinity.org/t/dfx-0-7-1-released-with-breaking-changes/4803): > > Hey guys, dfx 0.7.1 is now promoted to the latest release. There is a breaking change you should be aware of detailed here: To summarize, in previous releases, dfx canister call would proxy all calls via the cycle wallet by default. This is no longer the case. If a user expects the dfx canister call to proxy via the wallet, the user will have to do dfx canister --wallet=\ call now; this primarily impacts canisters that maintain an internal ACL based on the canister initializer. For example… --- _[View the full topic](https://forum.dfinity.org/t/identity-between-canister-owner-and-function-caller-are-not-equal/4874)._