mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #46249
[Bug 1744351] [NEW] Public key expiration date is current date for service access tokens
Public bug reported:
In the 'Manage service users' area of the Mahara administration when you
generate a new token, the public key of the token has an expiration date
of the current date/time making the token un-usable.
This bug was replicated in a remote and locally installed instance of
Mahara.
When I tried to perform curl commands using this token I was redirected
to the Mahara login page, showing the token was not valid.
To replicate:
1. Login to Mahara and go to Administration->Web services->Configuration->Managae service access tokens
2. Input a username and generate the token
3. Notice the expiration date of the public key is the current date/time
of the server that the instance is running on
** Affects: mahara
Importance: Undecided
Status: New
** Summary changed:
- Public key expiration date is current date for service access tokens is current date
+ Public key expiration date is current date for service access tokens
** Description changed:
In the 'Manage service users' area of the Mahara administration when you
generate a new token, the public key of the token always has a token of
the current date and time.
-
- This means that when trying to run the
This bug was replicated in a remote and locally installed instance of
Mahara.
To replicate:
- 1. Login to Mahara and go to Administration->Web services->Configuration->
+ 1. Login to Mahara and go to Administration->Web services->Configuration->Managae service access tokens
+
+ 2. Input a username and generate the token
+
+ 3. Notice the expiration date of the public key is the current date/time
+ of the server that the instance is running on
** Description changed:
In the 'Manage service users' area of the Mahara administration when you
- generate a new token, the public key of the token always has a token of
- the current date and time.
+ generate a new token, the public key of the token always has a public
+ key with an expiration date which is the current date and time.
This bug was replicated in a remote and locally installed instance of
Mahara.
To replicate:
1. Login to Mahara and go to Administration->Web services->Configuration->Managae service access tokens
2. Input a username and generate the token
3. Notice the expiration date of the public key is the current date/time
of the server that the instance is running on
** Description changed:
In the 'Manage service users' area of the Mahara administration when you
- generate a new token, the public key of the token always has a public
- key with an expiration date which is the current date and time.
+ generate a new token, the public key of the token has an expiration date
+ of the current date/time making the token un-usable.
This bug was replicated in a remote and locally installed instance of
Mahara.
+
+ When I tried to perform curl commands using this token I was redirected
+ to the Mahara login page, showing the token was not valid.
To replicate:
1. Login to Mahara and go to Administration->Web services->Configuration->Managae service access tokens
2. Input a username and generate the token
3. Notice the expiration date of the public key is the current date/time
of the server that the instance is running on
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1744351
Title:
Public key expiration date is current date for service access tokens
Status in Mahara:
New
Bug description:
In the 'Manage service users' area of the Mahara administration when
you generate a new token, the public key of the token has an
expiration date of the current date/time making the token un-usable.
This bug was replicated in a remote and locally installed instance of
Mahara.
When I tried to perform curl commands using this token I was
redirected to the Mahara login page, showing the token was not valid.
To replicate:
1. Login to Mahara and go to Administration->Web services->Configuration->Managae service access tokens
2. Input a username and generate the token
3. Notice the expiration date of the public key is the current
date/time of the server that the instance is running on
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1744351/+subscriptions
Follow ups
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Robert Lyon, 2018-04-05
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Kristina Hoeppner, 2018-03-08
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Robert Lyon, 2018-03-06
-
[Bug 1744351] A change has been merged
From: Mahara Bot, 2018-03-06
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Robert Lyon, 2018-03-06
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Steven, 2018-03-06
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Alex Buckley, 2018-01-23
-
[Bug 1744351] A patch has been submitted for review
From: Mahara Bot, 2018-01-22
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Robert Lyon, 2018-01-22
-
[Bug 1744351] Re: Public key expiration date is current date for service access tokens
From: Robert Lyon, 2018-01-22