Refactoring to Simplify Chilli Service Activation by Creating a Reliance on the UAM Service. #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
modified: examples/index.html deleted: lib/core_md5.js modified: lib/index.js modified: lib/utils.js new file: package-linx.json modified: package.json modified: test/fixtures/uamservice.js modified: test/tests.js
Incorporated Section on Updates, Requirements For a Working BBSC & minor Refactoring (removing CHAP computation on Client Side and moving to Server Side)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Justification:
Using CHAP authentication was buggy and requires the use of the RADSECRET in hashing of the newly generated password. Furthermore,