Thread

I have disabled the ability for users to sign in at multiple locations with the same account. It seems to function correctly, but the error is simply, “You are not authorized to perform this action.”

Is there a way to make this more descriptive? I see there is “Someone is already logged in using this account” message in /system/expressionengine/language/english/login_lang.php

Is there something I’m doing wrong?

Using EE version 2.2.2

I don’t think the system shouldn’t be saying you’re not authorized, but rather, simply kicking out the previous logged-in session. Can you provide a little bit more information on the steps that are taken that bring you to see this error message?

Hey Reusser Design, LLC,

Christopher is right, that error message is not intended at all. Getting kicked out is what should happen.

I would love to see the steps you are taking to get to this error message as well.

Please let us know!

Cheers,

Thanks for the help, guys! In Admin > Security and Privacy > Security and Session I have the following options set:

- Control Panel Session Type: Session ID only
- User Session Type: Cookies and session ID
- Allow multiple log-ins from a single account?: No

Oddly enough, I was getting that error earlier, but now I am allowed to log in as the same user in two different browsers. 😕
Any idea why this could be? I tried switching “Control Panel Session Type” to Cookies and session ID and still was able to log in as the same user to two different browsers.

Hi Reusser Design, LLC,

With you being on 2.2.2, it’s likely part of some overall user session bugs that were in that release.

Is updating an option for you?

Cheers,

Dan,

I’d like to avoid this option if possible. However, if that is the only/best way I’ll do that!

Hey Reusser,

Have you had a chance to upgrade?

Please let us know how it goes?

Cheers,

Shane,

Oops! Sorry. I thought I was waiting for you to provide a potential option before going the upgrade route. D’oh!

Is there a way to fix this without upgrading?

Hey Reusser,

I think what Dan is saying is that this is probably been fixed in later versions so upgrading is the path we would like you to take.

Does that work?

Cheers,

Shane,

Not a problem! I’ll discuss upgrading with the client and will report back if that does not fix the problem. Thanks for the help!

Hey Reusser,

Sounds good! I am glad we could help.

If you need anything else, please just let me know by opening a new thread.

Cheers,