Ron was also worried whether it would be possible to run the tests with real
authentication on.
Regards,
-marina
Bhakti Mehta wrote:
> Thanks to Shingwai and Anissa I found the actual fix for devtests is in
> this file
> devtests/appserv-tests/config.properties See the svn diff below.
> This file then regenerates the adminpassword.txt
> Question:
> Why is this change not committed to devtests workspace?
> Is this behaviour still subject to change?
>
> Shingwai mentioned he is still waiting for Bill to finalize. Bill should
> this change be commited so that the devtests run out of the box?
>
> Regards,
> Bhakti
>
> Index: config.properties
> ===================================================================
> --- config.properties (revision 25689)
> +++ config.properties (working copy)
> @@ -7,7 +7,7 @@
> https.port=8181
> http.host=localhost
> orb.port=3700
> -admin.password=adminadmin
> +admin.password=
> ssl.password=changeit
> master.password=changeit
> admin.password.file=${env.APS_HOME}/config/adminpassword.txt
>
>
>
>
> Shing Wai Chan wrote:
>
>> Bhakti Mehta wrote:
>>
>>> Sorry I was on vacation and have not been following this thread but
>>> atleast now I see if I unzip the latest bundle and try to run the
>>> devtests or cts all fail with this error
>>>
>>> deploy:
>>> [exec] Deprecated syntax, instead use:
>>> [exec] asadmin --port 4848 --host localhost --passwordfile
>>> /Users/bhakti/devtests/appserv-tests/config/adminpassword.txt --user
>>> admin deploy [options] ...
>>> [exec] Authentication failed for user: admin
>>> [exec] with password from password file:
>>> /Users/bhakti/devtests/appserv-tests/config/adminpassword.txt
>>> [exec] (Usually, this means invalid user name and/or password)
>>> [exec] Command deploy failed.
>>> [exec] Result: 1
>>>
>>> This is what is there in
>>> /Users/bhakti/devtests/appserv-tests/config/adminpassword.txt
>>> AS_ADMIN_PASSWORD=adminadmin
>>> AS_ADMIN_ADMINPASSWORD=adminadmin
>>
>> change this into
>> AS_ADMIN_ADMINPASSWORD=
>>
>> should work.
>> Shing Wai Chan
>>
>>> AS_ADMIN_MASTERPASSWORD=changeit
>>>
>>> This used to work out of the box. What more needs to be done for
>>> devtests and cts to pass?
>>>
>>> Regards,
>>> Bhakti Bill Shannon wrote:
>>>
>>>> Arun Gupta wrote on 9/17/09 5:28 PM:
>>>>
>>>>
>>>>> Each command execution in GlassFish shows the following output:
>>>>>
>>>>> ~/workspaces/glassfish/value-add/monitor/client-script
>>>>>
>>>>>
>>>>>> ~/tools/glassfish/v3/9-17/glassfishv3/bin/asadmin list-applications
>>>>>>
>>>>>
>>>>> Authentication failed with password from login store:
>>>>> /Users/arungupta/.asadminpass
>>>>> Enter admin password>
>>>>>
>>>>> If I do "asadmin login" then the anonymous login information is
>>>>> updated
>>>>> in .asadminpass.
>>>>>
>>>>> Do we expect our users to do this extra one-time step ?
>>>>>
>>>>
>>>>
>>>> Only if they have an existing .asadminpass that's configured with
>>>> different authentication information for the domain they're using.
>>>>
>>>> You've been following the long discussion we've had on this topic,
>>>> right?
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>