No video :(

#04: Ingress Controller with Last mile Security | Port Forwarding Explain | HTTPS | 1-way SSL

Подписаться 4,7 тыс.

Просмотров 2 тыс.

50% 1

#04: CloudHub 2.0 | Ingress Controller with Last mile Security | Port Forwarding Explain | HTTPS | 1-way SSL | Port Forwardin
In this video, we see how to deploy Mule Apps running on HTTPS and enable last mile security.
Thanks for watching this video!!!
References:
To see Mule Apps uploaded to Exchange: anypoint.mules...
Publish an Asset to Exchange Using Maven:
docs.mulesoft....
Connected Application Authentication:
docs.mulesoft....
Configure the CloudHub 2.0 Deployment Strategy:
docs.mulesoft....
Join this channel to get access to perks:
/ @muleaceacademy
#cloudhub2 #https #lastmilesecurity #rollingupdate #anypointplatform #apimanagement #apisecurity #mulesoft #mule4 #automation #exchange #runtimefabric

Опубликовано:

5 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 12

@sivachandramandalapu9892 Год назад

It's completely confusing. I didn't understand why you have enabled lastmile security option in oneway-ssl app to access the flow running on HTTPS-8081? whereas you didn't enable this option in twoway-ssl app to access the flow running on same HTTPs-8081. Could you please clarify this?

@MuleAceAcademy Год назад

1. Last Miles security option allows to reach server certificate to client 2. In two ssl in above case my end point is enabled with https but internal communication is two way ssl..let me know if you still have any questions

@sivachandramandalapu9892 Год назад

In the twoway-ssl app, what is the protocol of the client flow which was running on 8081? Since you didn’t enable ‘last mile security’, I presume it’s HTTP not HTTPS. Is my understanding correct?

@HrithikNaha Год назад

@@sivachandramandalapu9892 SSL must have been established in the second use case making last miles security redundant. All flows are in HTTPs I beleive but two way SSL was not established in the first use case hence last miles was used. Ashish can correct me if I'm wrong.

@sivachandramandalapu9892 Год назад

@@HrithikNaha Thank you.

@vivekravi5922 Год назад

Hi Sir, Last mile security and public url can we enable via Pipeline itself. added the pom.xml but not reflecting in anypoint platform. Please find below snippet added in pom.xml: ${publicURL} true true

@MuleAceAcademy Год назад

Yes we can enable. Please use maven version 3.8.1 and above. I am using below snippet and it works for me. Hope you are passing value for ${publicURL} via pipeline. true ${publicURL} true true

@priyankajoshi782 Год назад

hi Mule Ace Acedemy Thanks for clarifying about 8081 and 8082 but in case of DLB used in CH 1.0 the port mapping is 8091 (http) and 8092 (https ). Does these ports work as it is in CH 2.0 or there are any changes required

@MuleAceAcademy Год назад

CH2.0 only support 8081 only

@priyankajoshi782 Год назад

@@MuleAceAcademy So all the requests coming to Ingress is forwarded to 8081 . In case we are migrating from CH 1.0 we need to change all the inbound ports to 8081

@priyankajoshi782 Год назад

Thanks for the response much appreciated

@MuleAceAcademy Год назад

@@priyankajoshi782 Yes u r right