Activity log for bug #1744351

Date Who What changed Old value New value Message
2018-01-19 16:26:20 Alex Buckley bug added bug
2018-01-19 16:27:16 Alex Buckley summary 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
2018-01-19 16:28:24 Alex Buckley description 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-> 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 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
2018-01-19 16:28:54 Alex Buckley description 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 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 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. 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
2018-01-19 16:30:34 Alex Buckley description 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. 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 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
2018-03-06 02:47:40 Robert Lyon mahara: milestone 18.04.0
2018-03-06 02:47:45 Robert Lyon mahara: importance Undecided Low
2018-03-06 02:47:50 Robert Lyon mahara: status New Fix Committed
2018-03-08 19:00:57 Kristina Hoeppner tags usermanualupdate
2018-04-05 22:58:01 Robert Lyon mahara: status Fix Committed Fix Released