Removed IAL2_STRICT constant

[jmax-gsa]

🎫 Ticket

Link to the relevant ticket.

🛠 Summary of changes

Write a brief description of what you changed.

📜 Testing Plan

Provide a checklist of steps to confirm the changes.

• Step 1
• Step 2
• Step 3

👀 Screenshots

If relevant, include a screenshot or screen capture of the changes.

Before:

After:

🚀 Notes for Deployment

Include any special instructions for deployment.

[zachmargolis]

I would consider maybe deprecating this? # @deprecated or some other comment?

We have a few ServiceProviderIdentity rows that have ial = 22 in the DB in the int environment

ServiceProviderIdentity.where('ial > 2').pluck(:ial).tally
=> {3=>443, 22=>5}

On the other hand, int is not prod (and there are no IAL 22 in prod)

[jmhooper]

Since it's not in prod could we downgrade the dev/int users to IAL 2?

[jmhooper]

Meaning just an update for everyone with IAL = 22 to make them IAL 2?

[jmhooper]

I think we should handle the IAL2 strict users in int before merging. But, once we do that this should be good to go!

[jmhooper]

I just hopped on int and got rid of all the old IAL2-strict SP identities so this should be good to go