Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »


https://docs.128technology.com/docs/concepts_appid/#appid-based-on-tls


https://docs.128technology.com/docs/howto_ms365/#enable-module-learning-mode


4 ways to detect application:

  • module
  • TLS sni

https://junipernetworks.sharepoint.com/:w:/r/sites/128TImplementation/_layouts/15/Doc.aspx?sourcedoc=%7B57E0814D-4DBB-4698-949F-4E6BF05AE634%7D&file=SSR%20BCP%20-%20App%20ID.docx&action=default&mobileredirect=true

Order to identify application:


OptionsTLS , Module, HTTP
HTTP
  1. Using DNS to resolve FQDNs to IP addresses
TLS  SNIThis is done by inspecting the X.509 certificate sent by a server during the TLS handshake process. 
Module


Enabletls or/and module

Configuration > Authorization > Router > SELECT seattlesite1

go to :  Application Identification



5.4 Release

Configuration > Authorization > Router > Application Identification Settings 




In PCLI:

admin@128T-RTR-Branch-1.seattlesite1# shell
[admin@128T-RTR-Branch-1 ~]$ ls /etc/128technology/application-modules/
app_module_utils defaults office365.py
[admin@128T-RTR-Branch-1 ~]$


Documentation from Microsoft and link to the list of Microsoft IP address ( REST-API json)

https://docs.microsoft.com/en-us/microsoft-365/enterprise/microsoft-365-ip-web-service?view=o365-worldwide


View Application

Select a router


Create Service




Test servicesService configuration for every applications

IPsec



  • No labels