HI Nina ,


Could you please grant me POST access to
https://ambit.uni-plovdiv.bg:8443/ambit2/dataset/

my username is surajitray on the opentox LDAP

Regds
Surajit

On 9 March 2011 19:15, surajit ray <mr.surajit.ray at gmail.com> wrote:
> Hi ,
>
> I tried :
>
> curl -i -d "uri=https://ambit.uni-plovdiv.bg:8443/ambit2/dataset/" –d
> "action=POST" -d
> "subjectid=AQIC5wM2LY4SfcxzV1Iccj/JnoWbB6u8KYiuxgJt6QEFVH4=@AAJTSQACMDE=#"
> http://opensso.in-silico.ch/opensso/identity/authorize
>
> However I am getting
>
> HTTP/1.0 200 OK
> Server: nginx/0.6.32
> Date: Wed, 09 Mar 2011 13:43:21 GMT
> Content-Type: text/plain;charset=UTF-8
> Proxy-Connection: keep-alive
> Content-Length: 14
>
> boolean=false
>
>
> which means I cannot do a POST on the url
> https://ambit.uni-plovdiv.bg:8443/ambit2/dataset/
>
> also
>
> curl -i -d "uri=https://ambit.uni-plovdiv.bg:8443/ambit2/dataset/" –d
> "action=GET" -d
> "subjectid=AQIC5wM2LY4SfcxzV1Iccj/JnoWbB6u8KYiuxgJt6QEFVH4=@AAJTSQACMDE=#"
> http://opensso.in-silico.ch/opensso/identity/authorize
>
> yields the same results. Which is suprising since I can do a GET on
> that URL on the browser !
>
> Regards
> Surajit
>
> On 9 March 2011 19:10, Andreas Maunz <andreas at maunz.de> wrote:
>> Hi, I had a look at your policy. It looks syntactically correct, but you
>> definitely cannot (and need not) grant yourself access to Ambit. This is
>> Nina's job.
>> You should only create policies for your own resources.
>>
>> Andreas
>>
>> P.S: I am still trying to find out what happened to your policy, please
>> wait.
>>
>> surajit ray wrote on 03/09/2011 02:14 PM:
>>>
>>> Hi,
>>>
>>> curl -i -X GET http://opensso.in-silico.ch/Pol/opensso-pol -H
>>> "subjectid:AQIC5wM2LY4SfcyH9ELyynby356aOvAkimDZeEz2wzWTSX4=@AAJTSQACMDE=#"
>>>
>>> does not show the policy its saying it has created. It is not listing
>>> the created policies.
>>>
>>> Also I am attaching the policy file I am trying to use to get POST
>>> access to ambit. However a authorization thus
>>>
>>> curl -i -d "uri=https://ambit.uni-plovdiv.bg:8443/ambit2/dataset/" –d
>>> "action=POST" -d
>>> "subjectid=AQIC5wM2LY4SfcyH9ELyynby356aOvAkimDZeEz2wzWTSX4=@AAJTSQACMDE=#"
>>> http://opensso.in-silico.ch/opensso/identity/authorize
>>>
>>> yields
>>>
>>> HTTP/1.0 200 OK
>>> Server: nginx/0.6.32
>>> Date: Wed, 09 Mar 2011 13:12:06 GMT
>>> Content-Type: text/plain;charset=UTF-8
>>> Proxy-Connection: keep-alive
>>> Content-Length: 14
>>>
>>> boolean=false
>>>
>>>
>>> I am really confused if it has created a policy or not ? Or if it has
>>> made an incomplete policy !
>>>
>>> How can I get POST access to
>>> https://ambit.uni-plovdiv.bg:8443/ambit2/dataset/
>>>
>>> Regards
>>> Surajit
>>>
>>> On 9 March 2011 18:37, surajit ray<mr.surajit.ray at gmail.com>  wrote:
>>>>
>>>> Hi,
>>>>
>>>> the command
>>>>
>>>> curl -i -H "Content-Type: application/xml" -T /home/maxtox/maxtox.pol
>>>> -X POST http://opensso.in-silico.ch/Pol/opensso-pol -H
>>>>
>>>> "subjectid:AQIC5wM2LY4SfcyH9ELyynby356aOvAkimDZeEz2wzWTSX4=@AAJTSQACMDE=#"
>>>>
>>>> to create a policy returns
>>>>
>>>> HTTP/1.0 500 Internal Server Error
>>>> Server: nginx/0.6.32
>>>> Date: Wed, 09 Mar 2011 13:02:39 GMT
>>>> Content-Type: text/plain
>>>> Proxy-Connection: keep-alive
>>>> Content-Length: 44
>>>>
>>>> IOException. Please contact administrator.
>>>>
>>>> I was expecting that it did not create the policy since I did not 200
>>>> OK. However when I ran the same again I got
>>>>
>>>> HTTP/1.0 400 Bad Request
>>>> Server: nginx/0.6.32
>>>> Date: Wed, 09 Mar 2011 13:04:26 GMT
>>>> Content-Type: text/plain
>>>> Proxy-Connection: keep-alive
>>>> Content-Length: 111
>>>>
>>>> OpenSSOPolicy allow_ambit_dataset_access_for_maxtox already exists in
>>>> organization dc=opensso,dc=java,dc=net.
>>>>
>>>>
>>>> which means it created the policy. Therefore it should have given a
>>>> 200 OK before. Or is this policy invalid ?
>>>>
>>>> Regards
>>>> Surajit
>>>>
>>>>
>>>>
>>>> On 9 March 2011 18:30, surajit ray<mr.surajit.ray at gmail.com>  wrote:
>>>>>
>>>>> Hi Andreas,
>>>>>
>>>>> Documentation at
>>>>>
>>>>> http://opentox.org/dev/documentation/Guidance%20on%20Using%20AA#example-session-policies
>>>>>
>>>>> incorrectly states that the subjectid should be URL encoded. The command
>>>>>
>>>>> curl -i -X GET http://opensso.in-silico.ch/Pol/opensso-pol -H
>>>>>
>>>>> "subjectid:AQIC5wM2LY4SfcyH9ELyynby356aOvAkimDZeEz2wzWTSX4%3D%40AAJTSQACMDE%3D%23"
>>>>>
>>>>> returns .......
>>>>>
>>>>> HTTP/1.0 400 Bad Request
>>>>> Server: nginx/0.6.32
>>>>> Date: Wed, 09 Mar 2011 12:57:15 GMT
>>>>> Content-Type: text/plain
>>>>> Proxy-Connection: keep-alive
>>>>> Content-Length: 59
>>>>>
>>>>> Token could not be resolved to a user id. Token expired?.
>>>>>
>>>>>
>>>>>
>>>>> While the same without url encoding
>>>>> curl -i -X GET http://opensso.in-silico.ch/Pol/opensso-pol -H
>>>>>
>>>>> "subjectid:AQIC5wM2LY4SfcyH9ELyynby356aOvAkimDZeEz2wzWTSX4=@AAJTSQACMDE=#"
>>>>>
>>>>> returns
>>>>>
>>>>>
>>>>> HTTP/1.0 200 OK
>>>>> Server: nginx/0.6.32
>>>>> Date: Wed, 09 Mar 2011 12:57:22 GMT
>>>>> Content-Type: text/plain
>>>>> Proxy-Connection: keep-alive
>>>>> Content-Length: 1
>>>>>
>>>>>
>>>>>
>>>>> Could you please change the same on the documentation page ?
>>>>>
>>>>> Regards
>>>>> Surajit
>>>>>
>>>>>
>>>>>
>>>>> On 8 March 2011 19:07, Andreas Maunz<andreas at maunz.de>  wrote:
>>>>>>
>>>>>> surajit ray wrote on 03/08/2011 02:23 PM:
>>>>>>>
>>>>>>> Could you please clarify these inconsistencies (if the cannot be
>>>>>>> changed) in the help document ?
>>>>>>
>>>>>> Definitely, I'll make the point more explicit.
>>>>>>
>>>>>> Andreas
>>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>> --
>> http://www.maunz.de
>>
>>            According to my calculations the problem doesn't exist.
>>
>
>
>
> --
> Surajit Ray
> Partner
> www.rareindianart.com
>



-- 
Surajit Ray
Partner
www.rareindianart.com