Problem with authentication on 0.7.1

Bug #599136 reported by Oliver Röss

This bug report was converted into a question: question #116004: What is the correct api key for a locally deployed server?.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TAC Energy
Invalid
Undecided
Unassigned

Bug Description

I deployed the new server locally and noticed that none of my client's shouts got registered. I looked into the server log and found this:

2010-06-27 22:30:16,222 [queueManagementReceiveShoutNotificationJmsListenerContainer-1] ERROR grails.app.service.edu.kit.iism.cdamarket.QueueManagementService - Error creating new shout: Cannot authorize user admin: Wrong or missing username or apiKey
org.springframework.security.BadCredentialsException: Cannot authorize user admin: Wrong or missing username or apiKey

Before 0.7.1, the username was 'admin' and the apikey was 'testit'. I can login with these credentials but the client doesn't seem to be able to authenticate with them.

Revision history for this message
Carsten Block (cblock) wrote :

Hi!

Please use the username "admin" and the specific api key displayed in the admin user properties. To show the user properties, log in to you local server and then click on the "admin" user name on the top right of the server's welcome screen.

Changed in tacenergy:
status: New → Won't Fix
Revision history for this message
Carsten Block (cblock) wrote :

For security reasons, the admin's api key is no longer statically set to "secret" but dynamcially assigned upon the first server startup. Please look-up the api key on the admin's user page (click on the "admin" username on the top right of the welcome screen after having logged in).

Changed in tacenergy:
status: Won't Fix → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.