[OPENAM-14831] Default 'OAuth2 Access Token Modification Script' not populated after an upgrade to AM 7.0 Created: 29/Apr/19  Updated: 23/May/19  Resolved: 15/May/19

Status: Resolved
Project: OpenAM
Component/s: oauth2, scripting
Affects Version/s: 7.0.0
Fix Version/s: 6.5.2, 7.0.0

Type: Bug Priority: Major
Reporter: Andy Itter Assignee: Dipu Seminlal
Resolution: Fixed Votes: 0
Labels: AME, Must-Fix, NEWTON
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Rank: 1|hzxqnr:
Sprint: AM 2019.7 - Lighthouse
Verified Version/s:

 Description   

Bug description

The default 'OAuth2 Access Token Modification Script' is not populated after an upgrade from AM 6.5 to AM 7.0 master.

How to reproduce the issue

1). Install an earlier version of AM, eg 6.5.x

2). Upgrade to 7.0 master

3). Go to Scripts > OAuth2 Access Token Modification Script - note that the script is empty.

Expected behaviour
Default script is populated
Current behaviour
Default script is empty


 Comments   
Comment by Chris Lee [ 29/Apr/19 ]

Unverified, but it looks like if there was an existing OAuth2 provider before the upgrade, there's nothing that would add the `OAuth2 Access Token Modification Script` property during the upgrade (based on `OAuth2ProviderUpgradeHelper` mentioning `OIDC_CLAIMS_EXTENSION_SCRIPT`, but not the OAuth2 access token script).

Comment by Ľubomír Mlích [ 23/May/19 ]

I can see OAuth2 Access Token Modification Script in AM 6.5.2-M3 after upgrade from AM 6.5.1 with created Oauth2 Provider. Script is set to use in Oauth2 provider configuration

Generated at Fri Mar 05 06:31:29 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.