You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When EPS authentication service is enabled, the Orc8r needs to stop streaming subscriber information to Subscriberdb on AGW. As part of this change, the APN specific configs, such as static IP address(es), vlan-id, etc, which are needed by Mobilityd on AGW will not be streamed.
This issue tracks the steps needed to make the config available to Mobilityd when EPS authentication service is used for authentication instead of AGW's SubscriberDB. Specifically,
The text was updated successfully, but these errors were encountered:
ssanadhya
changed the title
[AGW + Orc8r] Remove subscriberDB streaming when EPS authentication service is active
[AGW + Orc8r] Replace subscriberDB streaming when EPS authentication service is active
Jul 8, 2022
Do we have some more information about the content of the changes that needs to be documented? Is everything in this ticket, the linked security issue, and the linked PRs?
Also, which features should be tested? I assume this would need to be a federated integration test since it involves AGW and Orc8r?
It looks like #13252 and #13251 are not done but were closed by the stalebot. So there is probably more left to do than writing tests and documentation.
In order to address #12907, #13048 adds logic to enable EPS authentication service in Orc8r whenever the CloudSubscriberdbEnabled flag is set to true.
When EPS authentication service is enabled, the Orc8r needs to stop streaming subscriber information to Subscriberdb on AGW. As part of this change, the APN specific configs, such as static IP address(es), vlan-id, etc, which are needed by Mobilityd on AGW will not be streamed.
This issue tracks the steps needed to make the config available to Mobilityd when EPS authentication service is used for authentication instead of AGW's SubscriberDB. Specifically,
The text was updated successfully, but these errors were encountered: