Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6044903
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T07:03:55+00:00 2026-05-23T07:03:55+00:00

I am upgrading a legacy Grails application and also upgrade the acegi plugin from

  • 0

I am upgrading a legacy Grails application and also upgrade the acegi plugin from 0.4 to 0.5.2. When I try to log into the application, I am getting a BadCredentialsException: with “User does not exist”.

The user definitely exists in the database and the credentials are definitely correct. I don’t know much about the acegi plugin but have been reading up and from what I understand there should not have been any upgrade issues. I am also upgrading Grails from 1.0.3 to 1.3.7 at the same time, so that could be related to. Any other ideas?

Thanks.

org.springframework.security.event.authentication.AuthenticationFailureBadCredentialsEvent[source=org.springframework.security.providers.UsernamePasswordAuthenticationToken@9a501e93: Principal: bwalsh@pps.com; Password: [PROTECTED]; Authenticated: false; Details: org.springframework.security.ui.WebAuthenticationDetails@380f4: RemoteIpAddress: 127.0.0.1; SessionId: 915D5CDB8F5A0AE07EC13F435FA66690; Not granted any authorities]
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T07:03:55+00:00Added an answer on May 23, 2026 at 7:03 am

    BadCredentialsException means the password check failed. Looks like a misconfiguration of the password hashing algorithm – is the algorithm attribute set correctly?

    The default is

    algorithm = 'SHA'
    

    but it should be overridden in your SecurityConfig.groovy if you use a different approach.

    btw – you should be upgrading to http://grails.org/plugin/spring-security-core 🙂

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Ok, so we're upgrading a client's legacy code from 2.0.2 to latest rails. Most
Also, I'm wondering what effect upgrading to Ruby 1.9 would have on legacy code
I'm getting a weird error from my sites ever since upgrading to Windows 2008
After upgrading my copy of xcode from 3.2.2 to 3.2.3, I am getting over
While upgrading a Windows Forms application from the .NET 1.1 framework to the .NET
After upgrading a rails 1.2 website to 2.1, the ExceptionNotifier plugin no longer works,
We're upgrading an existing program from Win2k/SQL Server 2k to Windows 2003 and SQL
We're looking at upgrading from Visual Studio 2005 to Visual Studio 2008. I discovered
I'm upgrading an app with many different settings files from XP to Vista and
I have encountered a weird situation while updating/upgrading some legacy code. I have a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.