To: oauth@ietf.org
Cc: oauth-bounces@ietf.org
MIME-Version: 1.0
Message-ID: <OF89C2383F.5888D4B7-ON85257AF6.005D229B-85257AF6.0063BA05@us.ibm.com>
From: Todd W Lainhart <lainhart@us.ibm.com>
Date: Thu, 17 Jan 2013 13:09:17 -0500
Content-Type: multipart/alternative;
 boundary="=_alternative 0063BA0385257AF6_="
Subject: [OAUTH-WG] error_description USASCII-encoded - is this a difficulty?
Precedence: list

This is a multipart message in MIME format.
--=_alternative 0063BA0385257AF6_=
Content-Type: text/plain; charset="US-ASCII"

We're working on an OAuth 2.0 AS, with extensions defined for session 
mgmt.  We're trying to adopt uniformly the error reporting mechanism in 
6749.

I'm now realizing that the error_description response in specified to be 
USASCII.  I was assuming that the error message could be UTF-8 encoded, 
such that I could return error messages in the client's locale.  E.G. 
consider the client credentials grant.  The store on the AS holding the 
registration is down, so I'd like to return a 500 with an error message 
from the store, from a catalog mapped to the client's language.

I've wondered about adding an additional response parameter, something 
like error_description_locale, but thought that there might be better 
practices out there.  I'm also wondering about the USASCII constraint on 
error_description.  I'm a long-time reader of this list, but I'm not 
recalling the background on this.





Todd Lainhart
Rational software
IBM Corporation
550 King Street, Littleton, MA 01460-1250
1-978-899-4705
2-276-4705 (T/L)
lainhart@us.ibm.com

--=_alternative 0063BA0385257AF6_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">We're working on an OAuth 2.0 AS, with
extensions defined for session mgmt. &nbsp;We're trying to adopt uniformly
the error reporting mechanism in 6749.</font>
<br>
<br><font size=2 face="sans-serif">I'm now realizing that the error_description
response in specified to be USASCII. &nbsp;I was assuming that the error
message could be UTF-8 encoded, such that I could return error messages
in the client's locale. &nbsp;E.G. consider the client credentials grant.
&nbsp;The store on the AS holding the registration is down, so I'd like
to return a 500 with an error message from the store, from a catalog mapped
to the client's language.</font>
<br>
<br><font size=2 face="sans-serif">I've wondered about adding an additional
response parameter, something like error_description_locale, but thought
that there might be better practices out there. &nbsp;I'm also wondering
about the USASCII constraint on error_description. &nbsp;I'm a long-time
reader of this list, but I'm not recalling the background on this.<br>
</font>
<br>
<table width=223 style="border-collapse:collapse;">
<tr height=8>
<td width=223 bgcolor=white style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=1 face="Verdana"><b><br>
<br>
<br>
Todd Lainhart<br>
Rational software<br>
IBM Corporation<br>
550 King Street, Littleton, MA 01460-1250</b></font><font size=1 face="Arial"><b><br>
1-978-899-4705<br>
2-276-4705 (T/L)<br>
lainhart@us.ibm.com</b></font></table>
<br>
--=_alternative 0063BA0385257AF6_=--