[Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

View: New views
13 Messages — Rating Filter:   Alert me  

[Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Anissa Lam :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or
keep it as   'on|off|inherit'.   Actually i have 'temp' change that to
make the verifier happy,  but not sure if thats  the right thing,  or
masking another bug.

thanks
Anissa.

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by jluehe :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Anissa,

On 10/15/09 18:34, Anissa Lam wrote:

I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or keep it as   'on|off|inherit'.   Actually i have 'temp' change that to make the verifier happy,  but not sure if thats  the right thing,  or masking another bug.

I did some research and found that the change was made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113

The web container uses ConfigBeansUtilities#toBoolean to evalute these props,
which interprets "true", "on", "yes", and "1" as enabled.

Therefore, my preference would be to accept "true|on|false|off|inherit' as legal values.


Jan



thanks
Anissa.



Subject:
sso-enabled and access-logging-enabled attribute changed recently ?
From:
Anissa Lam Anissa.Lam@...
Date:
Tue, 13 Oct 2009 17:25:59 -0700
To:
admin@...
To:
admin@...

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...


Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Nandini Ektare-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On Oct 15, 2009, at 6:51 PM, Jan Luehe wrote:

Anissa,

On 10/15/09 18:34, Anissa Lam wrote:

I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or keep it as   'on|off|inherit'.   Actually i have 'temp' change that to make the verifier happy,  but not sure if thats  the right thing,  or masking another bug.

I did some research and found that the change was made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113

The web container uses ConfigBeansUtilities#toBoolean to evalute these props,
which interprets "true", "on", "yes", and "1" as enabled.

Therefore, my preference would be to accept "true|on|false|off|inherit' as legal values.

Jan: I can change the enum to include all five values. 

Anissa: do you have any issues with this?

Nandini


Jan



thanks
Anissa.



Subject:
sso-enabled and access-logging-enabled attribute changed recently ?
From:
Anissa Lam Anissa.Lam@...
Date:
Tue, 13 Oct 2009 17:25:59 -0700
To:
admin@...
To:
admin@...

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...



Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by jluehe :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 10/15/09 19:30, Nandini Ektare wrote:

On Oct 15, 2009, at 6:51 PM, Jan Luehe wrote:

Anissa,

On 10/15/09 18:34, Anissa Lam wrote:

I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or keep it as   'on|off|inherit'.   Actually i have 'temp' change that to make the verifier happy,  but not sure if thats  the right thing,  or masking another bug.

I did some research and found that the change was made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113

The web container uses ConfigBeansUtilities#toBoolean to evalute these props,
which interprets "true", "on", "yes", and "1" as enabled.

Therefore, my preference would be to accept "true|on|false|off|inherit' as legal values.

Jan: I can change the enum to include all five values.

That would be great!

Jan


Anissa: do you have any issues with this?

Nandini


Jan



thanks
Anissa.



Subject:
sso-enabled and access-logging-enabled attribute changed recently ?
From:
Anissa Lam Anissa.Lam@...
Date:
Tue, 13 Oct 2009 17:25:59 -0700
To:
admin@...
To:
admin@...

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...




Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Nandini Ektare-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Oct 15, 2009, at 7:54 PM, Jan  wrote:

On 10/15/09 19:30, Nandini Ektare wrote:

On Oct 15, 2009, at 6:51 PM, Jan Luehe wrote:

Anissa,

On 10/15/09 18:34, Anissa Lam wrote:

I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or keep it as   'on|off|inherit'.   Actually i have 'temp' change that to make the verifier happy,  but not sure if thats  the right thing,  or masking another bug.

I did some research and found that the change was made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113

The web container uses ConfigBeansUtilities#toBoolean to evalute these props,
which interprets "true", "on", "yes", and "1" as enabled.

Therefore, my preference would be to accept "true|on|false|off|inherit' as legal values.

Jan: I can change the enum to include all five values.

That would be great!

Done. (I assume you want the same in http-service too. Right? )

-Nandini

Diffs:
config-api glassfish$ svn diff 
Index: src/main/java/com/sun/enterprise/config/serverbeans/VirtualServer.java
===================================================================
--- src/main/java/com/sun/enterprise/config/serverbeans/VirtualServer.java (revision 32831)
+++ src/main/java/com/sun/enterprise/config/serverbeans/VirtualServer.java (working copy)
@@ -230,7 +230,7 @@
      * @return possible object is {@link String }
      */
     @Attribute(defaultValue = "inherit")
-    @Pattern(regexp="(true|false|inherit)")
+    @Pattern(regexp="(true|on|false|off|inherit)")
     String getSsoEnabled();
 
     /**
@@ -246,7 +246,7 @@
      * @return possible object is {@link String }
      */
     @Attribute(defaultValue = "inherit")
-    @Pattern(regexp="(true|false|inherit)")
+    @Pattern(regexp="(true|on|false|off|inherit)")
     String getAccessLoggingEnabled();
 
     /**

 Jan


Anissa: do you have any issues with this?

Nandini


Jan



thanks
Anissa.



Subject:
sso-enabled and access-logging-enabled attribute changed recently ?
From:
Anissa Lam Anissa.Lam@...
Date:
Tue, 13 Oct 2009 17:25:59 -0700
To:
admin@...
To:
admin@...

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...





Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Anissa Lam :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Nandini,

Nandini Ektare wrote:

On Oct 15, 2009, at 6:51 PM, Jan Luehe wrote:

Anissa,

On 10/15/09 18:34, Anissa Lam wrote:

I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or keep it as   'on|off|inherit'.   Actually i have 'temp' change that to make the verifier happy,  but not sure if thats  the right thing,  or masking another bug.

I did some research and found that the change was made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113

The web container uses ConfigBeansUtilities#toBoolean to evalute these props,
which interprets "true", "on", "yes", and "1" as enabled.

Therefore, my preference would be to accept "true|on|false|off|inherit' as legal values.

Jan: I can change the enum to include all five values. 

Anissa: do you have any issues with this?
I am fine with whatever the decision,  as long as i get a clear answer.   As of now, it is accepting  "true | false | inherit"  but not "on | off".   I have already changed the GUI code to "true | false | inherit".  
I don't know if doc needs to be changed if it  no longer takes "on | off"  like before.

thanks
Anissa.

Nandini


Jan



thanks
Anissa.



Subject:
sso-enabled and access-logging-enabled attribute changed recently ?
From:
Anissa Lam Anissa.Lam@...
Date:
Tue, 13 Oct 2009 17:25:59 -0700
To:
admin@...
To:
admin@...

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...

Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Nandini Ektare-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Anissa,

On Oct 15, 2009, at 10:29 PM, Anissa Lam wrote:

Hi Nandini,

Nandini Ektare wrote:

On Oct 15, 2009, at 6:51 PM, Jan Luehe wrote:

Anissa,

On 10/15/09 18:34, Anissa Lam wrote:

I didn't hear any response from the admin alias .   resend to the dev alias.
I need to know if GUI should change this to  'true|false|inherit'   or keep it as   'on|off|inherit'.   Actually i have 'temp' change that to make the verifier happy,  but not sure if thats  the right thing,  or masking another bug.

I did some research and found that the change was made in response to
https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113

The web container uses ConfigBeansUtilities#toBoolean to evalute these props,
which interprets "true", "on", "yes", and "1" as enabled.

Therefore, my preference would be to accept "true|on|false|off|inherit' as legal values.

Jan: I can change the enum to include all five values. 

Anissa: do you have any issues with this?
I am fine with whatever the decision,  as long as i get a clear answer.   As of now, it is accepting  "true | false | inherit"  but not "on | off".   I have already changed the GUI code to "true | false | inherit".  
I don't know if doc needs to be changed if it  no longer takes "on | off"  like before.

I checked in those two additional enum value couple of hours back. So it should take on|off also in addition to true|false|inherit if you update v3/admin/config-api sources.

thanks,
Nandini

thanks
Anissa.

Nandini


Jan



thanks
Anissa.



Subject:
sso-enabled and access-logging-enabled attribute changed recently ?
From:
Anissa Lam Anissa.Lam@...
Date:
Tue, 13 Oct 2009 17:25:59 -0700
To:
admin@...
To:
admin@...

Hi,

In promoted build 67,  GUI is able to pass in "on/off/inherit" for sso-enabled and access-logging-enabled attribute in virtual server.
But today,  I notice that backend is throwing an error.  It says:

Constraints for this bean violated.  Message = ssoEnabled must match "(true|false|inherit)"
same for accessLoggingEnabled.

Is this a bug in the verifier or this is an intended change ?
I hope it is not the latter.   I think its really too late in the development cycle to make change like that, and without sending out notification.  It will affect the console, doc and testing.

thanks
Anissa.


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...


--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@...


Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Justin Lee-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Agreed.

Jan Luehe wrote:

> Anissa,
>
> On 10/15/09 18:34, Anissa Lam wrote:
>>
>> I didn't hear any response from the admin alias .   resend to the dev
>> alias.
>> I need to know if GUI should change this to  'true|false|inherit'  
>> or keep it as   'on|off|inherit'.   Actually i have 'temp' change
>> that to make the verifier happy,  but not sure if thats  the right
>> thing,  or masking another bug.
>
> I did some research and found that the change was made in response to
> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113
>
> The web container uses ConfigBeansUtilities#toBoolean to evalute these
> props,
> which interprets "true", "on", "yes", and "1" as enabled.
>
> Therefore, my preference would be to accept
> "true|on|false|off|inherit' as legal values.
>
>
> Jan
>
>
>>
>> thanks
>> Anissa.
>>
>> ------------------------------------------------------------------------
>>
>> Subject:
>> sso-enabled and access-logging-enabled attribute changed recently ?
>> From:
>> Anissa Lam <Anissa.Lam@...>
>> Date:
>> Tue, 13 Oct 2009 17:25:59 -0700
>> To:
>> admin@...
>>
>> To:
>> admin@...
>>
>>
>> Hi,
>>
>> In promoted build 67,  GUI is able to pass in "on/off/inherit" for
>> sso-enabled and access-logging-enabled attribute in virtual server.
>> But today,  I notice that backend is throwing an error.  It says:
>>
>> *Constraints for this bean violated.  Message = ssoEnabled must match
>> "(true|false|inherit)"
>> *same for accessLoggingEnabled.
>>
>> Is this a bug in the verifier or this is an intended change ?
>> I hope it is not the latter.   I think its really too late in the
>> development cycle to make change like that, and *without* sending out
>> notification.  It will affect the console, doc and testing.
>>
>> thanks
>> Anissa.
>>
>> ------------------------------------------------------------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>  
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by llc :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I think we're creating a mess by accepting so many values (as a  
general principle).  It's sloppy.    We should stick to exactly what  
Boolean.valueOf() returns.

Why not "vrai" and "nyet" also?  Once the line is crossed, english-
centric seems unfair when I don't speak english.

Lloyd

On Oct 16, 2009, at 6:11 AM, Justin Lee wrote:

> Agreed.
>
> Jan Luehe wrote:
>> Anissa,
>>
>> On 10/15/09 18:34, Anissa Lam wrote:
>>>
>>> I didn't hear any response from the admin alias .   resend to the  
>>> dev alias.
>>> I need to know if GUI should change this to  'true|false|
>>> inherit'   or keep it as   'on|off|inherit'.   Actually i have  
>>> 'temp' change that to make the verifier happy,  but not sure if  
>>> thats  the right thing,  or masking another bug.
>>
>> I did some research and found that the change was made in response to
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113
>>
>> The web container uses ConfigBeansUtilities#toBoolean to evalute  
>> these props,
>> which interprets "true", "on", "yes", and "1" as enabled.
>>
>> Therefore, my preference would be to accept "true|on|false|off|
>> inherit' as legal values.
>>
>>
>> Jan
>>
>>
>>>
>>> thanks
>>> Anissa.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> Subject:
>>> sso-enabled and access-logging-enabled attribute changed recently ?
>>> From:
>>> Anissa Lam <Anissa.Lam@...>
>>> Date:
>>> Tue, 13 Oct 2009 17:25:59 -0700
>>> To:
>>> admin@...
>>>
>>> To:
>>> admin@...
>>>
>>>
>>> Hi,
>>>
>>> In promoted build 67,  GUI is able to pass in "on/off/inherit" for  
>>> sso-enabled and access-logging-enabled attribute in virtual server.
>>> But today,  I notice that backend is throwing an error.  It says:
>>>
>>> *Constraints for this bean violated.  Message = ssoEnabled must  
>>> match "(true|false|inherit)"
>>> *same for accessLoggingEnabled.
>>>
>>> Is this a bug in the verifier or this is an intended change ?
>>> I hope it is not the latter.   I think its really too late in the  
>>> development cycle to make change like that, and *without* sending  
>>> out notification.  It will affect the console, doc and testing.
>>>
>>> thanks
>>> Anissa.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>> For additional commands, e-mail: dev-help@...
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

Lloyd Chambers
lloyd.chambers@...
GlassFish Team




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: [Fwd: sso-enabled and access-logging-enabled attribute changed recently ?]

by Justin Lee-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I completely agree.  That would break backward compatibility, though.  
I'm ok with that, personally, if it means a little more sanity going
forward.

Lloyd Chambers wrote:

> I think we're creating a mess by accepting so many values (as a
> general principle).  It's sloppy.    We should stick to exactly what
> Boolean.valueOf() returns.
>
> Why not "vrai" and "nyet" also?  Once the line is crossed,
> english-centric seems unfair when I don't speak english.
>
> Lloyd
>
> On Oct 16, 2009, at 6:11 AM, Justin Lee wrote:
>
>> Agreed.
>>
>> Jan Luehe wrote:
>>> Anissa,
>>>
>>> On 10/15/09 18:34, Anissa Lam wrote:
>>>>
>>>> I didn't hear any response from the admin alias .   resend to the
>>>> dev alias.
>>>> I need to know if GUI should change this to  'true|false|inherit'  
>>>> or keep it as   'on|off|inherit'.   Actually i have 'temp' change
>>>> that to make the verifier happy,  but not sure if thats  the right
>>>> thing,  or masking another bug.
>>>
>>> I did some research and found that the change was made in response to
>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=10113
>>>
>>> The web container uses ConfigBeansUtilities#toBoolean to evalute
>>> these props,
>>> which interprets "true", "on", "yes", and "1" as enabled.
>>>
>>> Therefore, my preference would be to accept
>>> "true|on|false|off|inherit' as legal values.
>>>
>>>
>>> Jan
>>>
>>>
>>>>
>>>> thanks
>>>> Anissa.
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> Subject:
>>>> sso-enabled and access-logging-enabled attribute changed recently ?
>>>> From:
>>>> Anissa Lam <Anissa.Lam@...>
>>>> Date:
>>>> Tue, 13 Oct 2009 17:25:59 -0700
>>>> To:
>>>> admin@...
>>>>
>>>> To:
>>>> admin@...
>>>>
>>>>
>>>> Hi,
>>>>
>>>> In promoted build 67,  GUI is able to pass in "on/off/inherit" for
>>>> sso-enabled and access-logging-enabled attribute in virtual server.
>>>> But today,  I notice that backend is throwing an error.  It says:
>>>>
>>>> *Constraints for this bean violated.  Message = ssoEnabled must
>>>> match "(true|false|inherit)"
>>>> *same for accessLoggingEnabled.
>>>>
>>>> Is this a bug in the verifier or this is an intended change ?
>>>> I hope it is not the latter.   I think its really too late in the
>>>> development cycle to make change like that, and *without* sending
>>>> out notification.  It will affect the console, doc and testing.
>>>>
>>>> thanks
>>>> Anissa.
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@...
>>>> For additional commands, e-mail: dev-help@...
>>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@...
>> For additional commands, e-mail: dev-help@...
>>
>
> Lloyd Chambers
> lloyd.chambers@...
> GlassFish Team
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


container-based security?

by Luis del Campo Q :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Tomcat, by default, uses a simple tomcat-users.xml file to define users
and assign them roles at the same time. The file is located in the conf
directory.

To run a application that I am deploying I must define two users in this
file. But I have glassfish !!!

So, Where I can define users to use container-based security?

Thanks to all

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: container-based security?

by Kedar Mhaswade :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

GF has tools ;).

Use asadmin create-file-user command to create users for your applications.
We internally maintain a file (named keyfile) that contains user names,
SSHA hashes for passwords and group information.

-Kedar


Luis A. del Campo wrote:

> Tomcat, by default, uses a simple tomcat-users.xml file to define users
> and assign them roles at the same time. The file is located in the conf
> directory.
>
> To run a application that I am deploying I must define two users in this
> file. But I have glassfish !!!
>
> So, Where I can define users to use container-based security?
>
> Thanks to all
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


GF does not start.

by Luis del Campo Q :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi everyone at GF.

I installed *Sun GlassFish Enterprise Server 2.1* a few months ago and
it worked fine, but lately it does not want to start.

I see the Log file and there are many errors, and the first one is:

EMBEDDED Broker start failure:code = 1

What is happening?
Is there any solution for this issue?

Thanks in advance.

Regards

Luis.*
*

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...