Bug 1080226 - kronolith 'invalid token'
Summary: kronolith 'invalid token'
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: kronolith
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-25 00:39 UTC by David Benfell
Modified: 2024-07-08 22:03 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-08 22:03:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Benfell 2014-03-25 00:39:51 UTC
Description of problem:

kronolith allows initial access but rapidly starts bouncing user back to horde home screen saying 'invalid token'.


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. login to horde
2. select any calendar option
3.

Actual results: bounces back to horde home screen

Mar 24 03:12:06 munich HORDE: User is not authorized for kronolith [pid 5736 on line 306 of "/usr/share/pear/Horde/Registry.php"]
Mar 24 13:29:18 munich HORDE: User is not authorized for kronolith [pid 16594 on line 306 of "/usr/share/pear/Horde/Registry.php"]
Mar 24 13:29:24 munich HORDE: User is not authorized for kronolith [pid 16592 on line 306 of "/usr/share/pear/Horde/Registry.php"]


Expected results: selected function


Additional info: I'm a little reluctant to report this as I doubt I fully understand the problem. The horde FAQ is useless--and of course, *they* think it covers every contingency.

I assume this is really the same bug as one with IMP, which doesn't allow access at all and emits a similar log message to the one above, which I will seek to report separately and link back to this one.

Comment 1 David Benfell 2014-03-25 00:49:13 UTC
presumably related IMP bug is #1080228.

Comment 2 Troy Dawson 2024-07-08 22:03:02 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.


Note You need to log in before you can comment on or make changes to this bug.