[#740] Fix order dependency of setter methods when setAuthorizationMode(PRIVATE_KEY) is used

[er1c]

I have already signed the CLA.

Issue(s)

#740

Description

Un-necessary guards were added to prevent setting certain fields if the setAuthorizationMode hadn't been previously set. There are additional guards in place as part of the build() method.

Category

• Bugfix
• Enhancement
• New Feature
• Library Upgrade
• Configuration Change
• Versioning Change
• Unit or Integration Test(s)
• Documentation

Signoff

• I have submitted a CLA for this PR
• Each commit message explains what the commit does
• I have updated documentation to explain what my PR does
• My code is covered by tests if required
• I did not edit any automatically generated files

[JayNewstrom]

Thanks for the PR @er1c I'll let Arvind review.

[er1c]

@arvindkrishnakumar-okta feel free to steal/create a new PR/whatever if you still want the guards in place in the actual setter methods.

[er1c]

I just put the setter method asserts back in, and fixed miss-naming of the assertion message input parameter names.

[er1c]

@arvindkrishnakumar-okta friendly ping :)

[arvindkrishnakumar-okta]

@arvindkrishnakumar-okta friendly ping :)

Reviewed it and looks good to me. Thank you!