On 27/02/13 14:27, Colm O hEigeartaigh wrote:
Hi Sergey,
I guess using the name of the framework might be problematic when using
Syncope within some custom deployments; I'd vote for getting the realm name
customized via a property, and defaulted to a more neutral name as
suggested (say Identity Provision or Management, etc) or may be just
omitted during the challenge by default,
I will just change it to "Apache Syncope authentication" for now.
Thinking more about it, this is probably the best default option indeed,
you are all right :-)
Cheers, Sergey
The
ability to make it customisable via a property seems reasonable, could log
a JIRA for it?
Colm.
On Wed, Feb 27, 2013 at 2:14 AM, Sergey Beryozkin<[email protected]>wrote:
Hi
On 27/02/13 07:49, Francesco Chicchiriccň wrote:
On 26/02/2013 23:03, Colm O hEigeartaigh wrote:
Hi all,
The core's RestServiceExceptionMapper defines the following:
private static final String BASIC_REALM_UNAUTHORIZED = "Basic
realm=\"Spring Security Application\"";
I propose to change this to a more neutral realm, as this appears when
authenticating to access the new CXF-based REST API as well.
+1
Any objections or suggestions?
What about "Apache Syncope authentication"?
I guess using the name of the framework might be problematic when using
Syncope within some custom deployments; I'd vote for getting the realm name
customized via a property, and defaulted to a more neutral name as
suggested (say Identity Provision or Management, etc) or may be just
omitted during the challenge by default,
Thanks, Sergey
Regards.
