Skip to content
This repository was archived by the owner on May 23, 2025. It is now read-only.
This repository was archived by the owner on May 23, 2025. It is now read-only.

SEP-12: default to memo type of ID #683

Open
@yuriescl

Description

@yuriescl

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:

  1. Generate a non-custodial SEP-10 token, that is, without a memo attached
  2. Use that SEP-10 token to call SEP-12 PUT /customer, and put memo=1 in the payload fields
  3. Polaris will accept the request and let me edit any customer by putting any memo= value in the payload
  4. 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:

  1. Call SEP-12 PUT /customer with a memo=1 in the payload, but without memo_type
  2. Polaris will raise an error saying the memo doesn't match the memo_type
  3. Is this intended behavior?

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions