mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

The problem of the public key expires is an issue with reading the date
from the xmlrpc certificate - but as we are moving away from xmlrpc to
LTI we will ingore the problem with incorrect date for now.

Hiding that part of the form will avoid user confusion when not using
xmlrpc

-- 
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:
  Fix Committed

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