[Incident]: Some users report they are unable to access the case portal. Please see this community notice for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Network Block or IP Allow List for FlexNet Operations Cloud

Network Block or IP Allow List for FlexNet Operations Cloud

Introduction

This article provides the FlexNet Operations Cloud IP addresses for network block or IP allow listing (formerly referred to as "whitelisting").

Need to Know

A new set of network blocks is being used by FlexNet Operations Cloud services. Customers need to add these IP addresses to their existing network blocks by January 16, 2023, to ensure continued connectivity to FlexNet Operations Cloud UAT services. See the announcement here. Enforcement on Production is scheduled for February 18, 2023.

IPv4: 185.146.155.0/24

IPv6: 2620:122:f003::/48

The IP address blocks above may be broken down into more granular IP subnets based on environment:

Environment IPv4 Blocks IPv6 Blocks
Production 185.146.155.64/27 2620:122:f005::/56
UAT 185.146.155.0/27 2620:122:f003::/56
Production Copy Service (PCS) 185.146.155.32/27 2620:122:f004::/56

 

Best Practices

If you use an IP allow list, we require network blocks instead of individual IP addresses as the IP addresses for a given connection may change from one call to the next. We advise sharing the following network blocks to whitelist with your IT team:

IPv4: 185.146.155.0/24 

IPv6: 2620:122:f003::/48

-or-

Environment-specific IP address blocks to be added by users before the end of January 2023
Environment IPv4 Blocks IPv6 Blocks
Production 185.146.155.64/27 2620:122:f005::/56
UAT 185.146.155.0/27 2620:122:f003::/56
Production Copy Service (PCS) 185.146.155.32/27 2620:122:f004::/56

Note: It is no longer necessary to specify an IP address block for the Disaster Recovery (DR) environment.

 

Legacy IP address blocks to be deprecated on UAT on January 16, 2023
Environment IPv4 Blocks IPv6 Blocks
Production 64.14.29.0/24 2620:122:f001:1163::/64
UAT 64.14.29.0/24 2620:122:f001:1163::/64
Disaster Recovery (DR) 64.27.162.0/24 2620:122:f001:1163::1/128

 

Additional Resources

Frequently Asked Questions:

Understanding IP allow listing for FlexNet Operations Cloud -

Q: Why do we need to allow list these blocks?

A: If your organization, or your customers, operate strict firewall rules then you should allow these IP address blocks.

Q: Who should we speak to about allow listing?

A: You should discuss your needs with your IT administrators, who typically maintain these allow list rules. If you require further information, please contact Revenera Technical Support.

Q: Which FlexNet Operations Cloud services are affected if an allow list is configured?

A: All services can be impacted if you are using an allow list. Examples include:

  • Your employees connecting to the Producer Portal UI
  • Your end customers connecting to the Customer Portal UI
  • Your CRM system calls FNO Web Services
  • Your end customers' devices or Local License Servers making call-home or synchronization connections to FNO
  • Your end customers' devices connecting to Cloud License Servers to make Capability Requests

Q: Why do we need to configure an entire block – can't we just allow the IP address associated with the end point we use?

A: Our advice has always been to configure the block. When we move to AWS, this is even more important, because AWS does not allocate static IP addresses; the IP address allocated to a URL can change dynamically.

Understanding the AWS migration's affect on FlexNet Operations Cloud allow listing -

Q: If we do not use Cloud Licensing Service (CLS), why are all FlexNet Operations services affected by the allow list?

A: Our deployment in AWS will involve a single entry-point for connections to all services in FlextNet Operations, including Cloud Licensing Service (CLS). Once it is enabled for Cloud Licensing Service (CLS) it must be applied to all other services, even if they have not yet been migrated, to ensure correct communication between the services. 

Q: When will these changes take place?

A: The IP addresses were assigned on 2022-11-23, and so you should complete your allow list configuration before January 16, 2023 when the legacy IP address blocks are deprecated for the UAT. See the status page notification for schedule details. We will post another notification when these are scheduled to be deprecated for the Production environment.

Q: Why can't you continue to use the old IP address blocks indefinitely instead of using the new IP address blocks?

A: Using the legacy IP address blocks involves complex routing rules which will impact performance, and so we must move to the new blocks  as part of the AWS migration.

Q: What will happen if the addresses are not added to the allow list?

A: If you or your customers impose strict firewalls rules, the FlexNet Operations and Cloud Licensing Service (CLS) services may not be accessible.


Footnote: The terms "whitelisting" and "whitelist" have been replaced by "allow listing" and "allow list", respectively.   

Labels (4)
Was this article helpful? Yes No
100% helpful (2/2)
Comments

Could you also provide a list of tcp-ports that are used and should be 'open' on the client side ?

Hi,

We are whitelisting these URls in Firewalls 

1. https://flex<ID>.compliance.flexnetoperations.com/deviceservices

2. https://flex<ID>.compliance.flexnetoperations.com

Do we also need to do any changes ?

 

Version history
Last update:
‎Feb 02, 2023 11:36 AM
Updated by:
Contributors