You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might be a bug, or maybe it's intended behavior.
When calling the SEP-12 PUT /customer endpoint, I noticed that if I use a SEP-10 token without a custodial memo to authenticate the request, it let's me use memo as one of the fields in the payload. Shouldn't the authenticated SEP-10 account/memo be required to match the PUT /customer account/memo?
How to reproduce:
Generate a non-custodial SEP-10 token, that is, without a memo attached
Use that SEP-10 token to call SEP-12 PUT /customer, and put memo=1 in the payload fields
Polaris will accept the request and let me edit any customer by putting any memo= value in the payload
Is this intended behavior?
Also, apparently I also have to set memo_type=id in the payload, otherwise Polaris will raise an error saying the memo does not match memo_type. memo_type should default to id in SEP-12 calls, right?
How to reproduce:
Call SEP-12 PUT /customer with a memo=1 in the payload, but without memo_type
Polaris will raise an error saying the memo doesn't match the memo_type
Is this intended behavior?
The text was updated successfully, but these errors were encountered:
When calling the SEP-12 PUT /customer endpoint, I noticed that if I use a SEP-10 token without a custodial memo to authenticate the request, it let's me use memo as one of the fields in the payload.
This is the intended behavior, because SEP-31 senders don't include a memo in their SEP-10 challenge, since they're authenticating as themselves instead of as one of their users. Instead they have to specify the memos in their PUT /customer requests to identify their sending & receiving customers.
The downside is that this makes it possible for a SEP-6 wallet to omit their customer's memo in SEP-10. In reality though, this has minimal impact since anchors and custodial / omnibus wallets almost always have agreements and the wallet's public key is whitelisted on the anchor's backend.
Also, apparently I also have to set memo_type=id in the payload, otherwise Polaris will raise an error saying the memo does not match memo_type. memo_type should default to id in SEP-12 calls, right?
This might be a bug, or maybe it's intended behavior.
When calling the SEP-12
PUT /customer
endpoint, I noticed that if I use a SEP-10 token without a custodial memo to authenticate the request, it let's me usememo
as one of the fields in the payload. Shouldn't the authenticated SEP-10 account/memo be required to match thePUT /customer
account/memo?How to reproduce:
PUT /customer
, and putmemo=1
in the payload fieldsmemo=
value in the payloadAlso, apparently I also have to set
memo_type=id
in the payload, otherwise Polaris will raise an error saying thememo
does not matchmemo_type
.memo_type
should default toid
in SEP-12 calls, right?How to reproduce:
PUT /customer
with amemo=1
in the payload, but withoutmemo_type
memo
doesn't match thememo_type
The text was updated successfully, but these errors were encountered: