Bug 1924255

Summary: [RFE] Global Registration: Add character limit to the Token lifetime (hours) field
Product: Red Hat Satellite Reporter: Dhaval Joshi <dhjoshi>
Component: RegistrationAssignee: Leos Stejskal <lstejska>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.0CC: ahumbe, dsinglet, ehelms, jbhatia, lstejska
Target Milestone: 6.10.0Keywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:10:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dhaval Joshi 2021-02-02 21:08:13 UTC 
Description of problem:

On the global registration page, there should be some character limit to the field "Token lifetime (hours)".

For example - 32 digits or 64 digits


I've entered the below number and I did not get any error or warning message.
999999999999999999999999999999999999999999991111111111122222222222222444444444444444445555555555555555555558888888888888888888889999999999999999999900000000011111111112222222222333333333333334444444444445555555555555666666666666777777777788888889999999900000000099999999999999999999999999999999999999999999999991111111112222222222333333333333444444444444455555555555666666666677777777777777788888888889999999999999900000000000000001111111111111111111222222222222222222223333333333333333334444444444444444555555555555566666666666666666777777777777777777778888888888888888999999999999999900000000000000000

I was able to generate the below command successfully.

curl -X GET "https://dhjoshi-rhsat.syslab.pnq2.redhat.com:9090/register?activation_key=Custom_EPEL&location_id=2&operatingsystem_id=1&organization_id=1" -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjo0LCJpYXQiOjE2MTIzMDAwMjcsImp0aSI6IjQxOTY5NGI1OWFkNTA2MTM1ZWY5MGE4NmYzNDI0ODEyYTA1NWI1MjMzM2NmY2IxMDNhNjhhMWJhZGNhNGI5MzYiLCJleHAiOjM1OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5NjgwMDAwMDAwMDAwNDAwMDAwMDAwMDAwMDA4MDAwMDAwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDAwMDAwMDAwMTIwMDAwMDAwMDAwMDAwMDAwMDAwMDM5OTk5OTk5OTk5OTk5OTk5OTk2NDAwMDAwMDAwNDAwMDAwMDAwMDQwMDAwMDAwMDA0MDAwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDA0MDAwMDAwMDAwMDA0MDAwMDAwMDAwNDAwMDAwMDM5OTk5OTk2NDAwMDAwMDAzNTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5NjgwMDAwMDAwMDQwMDAwMDAwMDA0MDAwMDAwMDAwMDA0MDAwMDAwMDAwMDAwNDAwMDAwMDAwMDA0MDAwMDAwMDAwNDAwMDAwMDAwMDAwMDAwNDAwMDAwMDAwMDM5OTk5OTk5OTk5OTk2NDAwMDAwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDAwMDAwMDA0MDAwMDAwMDAwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDAwMDA0MDAwMDAwMDAwMDAwNDAwMDAwMDAwMDAwMDAwMDA0MDAwMDAwMDAwMDAwMDAwMDAwMDQwMDAwMDAwMDAwMDAwMDAzOTk5OTk5OTk5OTk5OTk2NDAwMDAwMDAwMDE2MTIzMDAwMjd9.GUZxo7TyJi5OXPfKAm2Q0gF4OVu1cWP2Xty4hf3G484' | bash
Comment 1 Bryan Kearney 2021-04-23 13:23:19 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31240 has been resolved.
Comment 5 errata-xmlrpc 2021-11-16 14:10:01 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702