check_atlassian not working in latest version

[rogerniesten]

Today we upgraded to the latest versions of BitBucket, Confluence and Jira and since that moment all three license checks stopped working:

Upgrade from - to:
BitBucket from 4.14.1 to 5.15
Confluence from 6.06 to 6.12.2
Jira from 7.3.2 to 7.12.3

Old situation (bitbucket example):
ATLASSIAN OK - Bitbucket (4.14.1, 0112953) license expires in 120 days | days_to_expiry=120;100;10 build_number=0112953;;

New situation:
ATLASSIAN CRITICAL - Could not find license expiry of Unknown product (5.15.0 bd5e9b4)

I've analysed your code a bit and noticed that in the old situation some meta tags were expected and existing in the page, but in the new versions,these tags are not existing anymore.

Is there any plan to update your check_atlassian script to the latest version of the Atlassian products?
Or do you know a way to force the Atlassian products to provide this data in meta data on their websites?

[t-8ch]

Unfortunately I don't know how to get the same information from newer Atlassian products without authentication. Even with authentication the script would probably need sysadmin permissions in the Application which would probably be a non-starter.

[rogerniesten]

Thanks for your feedback. I’ve found in two of the applications the information on another location of the site. (Could find it in the third application) I’ll fork your repo and will make an attempt to implement it. So probably you can expect a pull request in a few days…

[t-8ch]

@rogerniesten Thanks!
Could provide the information you found here, too?

[rogerniesten]

I've found the information for confluence (as number of days in daysBeforeMaintenanceExpiry) and jira (as epoch in maintenanceExpiry) for the expiration of the current license (actually the maintenance). Couldn't find this info for bitbucket yet. But unfortunately this information is only correctly populated when logged in to the application.
So unfortunately my assumption that I would be able to fix this issue is not correct :-(