Hello Everyone,

I am not able to debug, as the logs are not reflecting according to my
modification in the source code.

I changed

log.info(LogManager.getHeader(context, "auth", "attempting trivial auth of
user="+netid));


to


log.info(LogManager.getHeader(context, "auth", "attempting trivial LDAP
auth of user="+netid));



However, after re-building and installing , i still see no difference in
the log file.


I doubt, if the changes that i am making are reflecting in the build.


May i please ask for some help, about how to modify the source code,
compile, rebuild and deploy ( with the same database), using eclipse.


Thank you


Lohit



On Wed, Aug 29, 2012 at 11:38 AM, Lohit Valleru <[email protected]> wrote:

> Thank you for the quick reply, Helix.
>
> I knew, that the log is being printed from the xml module -
> authenticationutil class, and the meaning of result = 5, is nothing but the
> variable BAD_ARGS, which comes from the authentication method class.
>
> I have attached my modified LDAPHierarchicalAuthentication class to this
> mail.
>
> As you can see in the modified code. There is no place, where my
> modified LDAPHierarchicalAuthentication class, can return BAD_ARGS, except
> at one place : where the e-person check condition happens.
>
> However, before reaching that line, there is supposed to a be a log  - "No
> e-person found - So authenticating user"
>
> I do not find the above line in the log file, which means the code did not
> reach until that line.
>
> So i do not understand, from where is LDAPHierarchicalAuthentication is
> returning BAD_ARGS.
>
>
> Also this use-case, is useful in a special case, where the user will not
> be able to login to dspace, unless he is authenticated with kerberos
> password, which is done outside dspace environment.
>
> Just in case, I would also try integrating Dspace with kerberos in future,
> but before that, i would first want to be able to communicate without any
> password (as we do not use LDAP authentication/password verification - as
> it is unsecure)
>
> Thank you , i appreciate your help.
>
> Hopefully, we should be able to point out the issue.
>
>
> On Wed, Aug 29, 2012 at 10:55 AM, helix84 <[email protected]> wrote:
>
>> On Wed, Aug 29, 2012 at 4:44 PM, Lohit Valleru <[email protected]> wrote:
>> > 2012-08-29 09:35:34,545 INFO
>>  org.dspace.app.xmlui.utils.AuthenticationUtil
>> > @
>> >
>> anonymous:session_id=C370B01B65343E7705E6F2D0385F63C6:ip_addr=0:0:0:0:0:0:0:1%0:failed_login:email=lohit.valleru,
>> > realm=null, result=5"
>>
>> This gets printed here:
>>
>>
>> https://github.com/DSpace/DSpace/blob/dspace-1_8_x/dspace-xmlui/dspace-xmlui-api/src/main/java/org/dspace/app/xmlui/utils/AuthenticationUtil.java#L120
>>
>> Value of result:
>>
>>     /** User or password is not appropriate for this method. */
>>     public static final int BAD_ARGS = 5;
>>
>>
>> > occuring . Please do let me know, if i have to attach my modified code,
>> as i
>> > am not sure of the dspace-devel rules.
>>
>> Your modified LDAPHierarchicalAuthentication.java would sure be useful
>> to find the problem :)
>>
>> Judging from a quick reading of your email, you're doing it correctly.
>> There will surely be some detail that causes the problem.
>>
>> Although I don't understand your use-case. You will have a form with
>> only username? Why use usernames at all if anyone can impersonate
>> anyone else? You could just leave everything readable for the
>> Anonymous group (no need for authentication).
>>
>> Regards,
>> ~~helix84
>>
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to