- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 29, 2019
04:12 PM
The server team just disabled TLS 1.0 in our environment via GPO. It broke out integration with ITSM (Remedy). We re-enabled it and it is workig now. How do we make App Portal TLS 1.2 compliant?
We have .Net Framework 3.5 and 4.6 installed. Can we upgrade to 4.7?
2 Solutions
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 29, 2019
09:57 PM
TLS 1.2 is transparent to App Portal. You should be able to resolve your issue if you take a look at my responses to this other post here.
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Oct 10, 2019
08:42 PM
Thank you jdempsey, we did add those registry entries from the article but also needed to upgrade our .Net Framework to 4.7. Additionally, we added targetFramework="4.6"/ to the App Portal web.config file so the line was updated to: <httpRuntime maxRequestLength="40960" targetFramework="4.6"/> After we did that, we disabled TLS 1.0 and App Portal still was able to communicate with all of our external systems (SCCM, FNMS and Remedy).
This thread has been automatically locked due to inactivity.
To continue the discussion, please start a new thread.
3 Replies
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 29, 2019
04:13 PM
Forgot to mention we are on App Portal 2017 R2 SP1
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Aug 29, 2019
09:57 PM
TLS 1.2 is transparent to App Portal. You should be able to resolve your issue if you take a look at my responses to this other post here.
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Oct 10, 2019
08:42 PM
Thank you jdempsey, we did add those registry entries from the article but also needed to upgrade our .Net Framework to 4.7. Additionally, we added targetFramework="4.6"/ to the App Portal web.config file so the line was updated to: <httpRuntime maxRequestLength="40960" targetFramework="4.6"/> After we did that, we disabled TLS 1.0 and App Portal still was able to communicate with all of our external systems (SCCM, FNMS and Remedy).
