My mistake - the token used was produced before and after the Eperson became administrator, but without a "logout" in between.
On Tuesday, November 3, 2015 at 3:17:48 PM UTC+2, Evgeni Dimitrov wrote: > > I have one Eperson "AAAA", created during installation with "dspace > create-administrator". > > I have another Eperson "BBBB" created from the command line with: > dspace user --add -m [email protected] -p xxxx -g BB -s BB > > Both users are in the group "Administrator". > > I can login as "AAAA": > d:\apps\curl\curl -H "Content-Type: application/json" --data > "{\"email\":\"[email protected]\", \"password\":\"xxxx\"}" > http://localhost:8080/rest/login > > and I can create a collection: > > d:\apps\curl\curl -X POST -H "Content-Type: application/json" -H > "rest-dspace-token: NNNNNNNNNNNNNNNNNNNNNNNN" --data > "{\"name\":\"People\"}" > http://localhost:8080/rest/communities/3/collections > d:\adir\log > > > When I do the same with Eperson "BBBB", I do login, but when I try to > create the collection, I get "Unauthorized", "This request requires HTTP > authentication.". > > "BBBB" is administrator - I can login as "BBBB" to XMLUI and I can delete > the collection, but as if "BBBB" is not good enough to create the > collection?? > > Any ideas what may be wrong? > > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
