openid / connect / issues / #316 - Basic, Messages - phone_number format not specified — Bitbucket

Issue #316 resolved

Michael Jones created an issue 2011-11-17

Shouldn’t we mandate that phone_number has to follow the E.164 serialization?

Comments (3)

Nat Sakimura
I wish if we could, but it was intentionally left free format in the beginning to accommodate some of the existing implementations.
- 2011-11-17T17:59:24+00:00
Nat Sakimura
- assigned issue to
  
  Nat Sakimura
- changed status to open
RECOMMEND E.164.
- 2011-11-18T00:35:57+00:00
Nat Sakimura
- changed status to resolved
Fix ~~#316~~ - RECOMMEND E.164 as phone_number Basic, Messages

→ 0ad0a731bb5d
- 2011-11-21T08:08:02+00:00
Log in to comment

Assignee: Nat Sakimura

Type: bug

Priority: minor

Status: resolved

Component: –

Milestone: –

Version: –

Votes: 0

Watchers: 0

Jira: the preferred issue tracker for Bitbucket. Join the team!