Someone know that I am doing wrong?
Login
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-u "myuser:mypass" \
-X GET
http://quickstarts-edewit.rhcloud.com/rest/security/user/info
Update Contact
curl -v -b cookies.txt -c cookies.txt \
-H "Accept: application/json" \
-H "Content-type: application/json" \
-X PUT \
-d
'{"firstName":"fname","lastName":"lname","phoneNumber":"1234567","email":"example@example.com",
"birthDate":"2001-03-24"}' \
http://quickstarts-edewit.rhcloud.com/rest/contacts/7
— Passos
On Tue, May 20, 2014 at 3:13 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
Since we changed the use case for the Push part (now we broadcast) ,
passing a alias to UPS is not relevant anymore. For the login it's indeed
"loginName" to be passed in the auth header along with the password.
On Tue, May 20, 2014 at 7:34 PM, Daniel Passos <daniel(a)passos.me> wrote:
> To register I send "userName" and the login response
"loginName"?
>
> -- Passos
>
>
>
> On Thu, Apr 17, 2014 at 6:07 PM, Sebastien Blanc <scm.blanc(a)gmail.com>
> wrote:
>
>> Sure !
>> This is just a version to ease the client development.
>> I will ask PL team and Joshua their plans around HSTS and HTTPS.
>> In the mean time we can track all of this with
>>
https://issues.jboss.org/browse/AGPUSH-596
>>
>> Thx for the comment !
>> Sebi
>>
>>
>> On Thu, Apr 17, 2014 at 9:48 PM, Bruno Oliveira <bruno(a)abstractj.org>
>> wrote:
>>
>>> If your idea is to be secure, please make sure to use HTTPS and enforce
>>> users to be redirected. We did it in the past with HSTS on AG Security,
>>> might not be hard to copy & paste.
>>>
>>> Sebastien Blanc wrote:
>>> > And because I love you, I deployed on OpenShift a version of this
>>> secured
>>> > backend to ease the development of the clients !
>>> >
>>> > If you browse to
http://contacts-sblanc.rhcloud.com/ you will even
>>> see the
>>> > mobile web client. This deployed version contains also the Push
>>> Message
>>> > endpoint.
>>>
>>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev