Hi All,
We have discussed with the Kernel team and they have also suggested not use
${carbon.management.port}. We'll change to support ${mgt.transport.https.port}
and ${mgt.transport.http.port} placeholders instead of ${
carbon.management.port}.
Thanks!
*Jayanga Kaushalya*
Software Engineer
Mobi
Since there is a parameter available in the kernel, can't we use the same
thing rather than using a new one?
BTW, this will be an issue for ESB and all other products having custom
transports defined in the axis2.xml file when they try to use identity
related features.
Thanks,
NuwanD.
On Thu, De
Hi Lakmali,
This port is used in the Kernal and we have to check why it is returning
the NIO port. We are using the same code as in Kernal to get the value for
this. Will check with the Kernal team and inform further.
Thanks!
*Jayanga Kaushalya*
Software Engineer
Mobile: +94777860160
WSO2 Inc. |
Hi IS Team,
The variable "${carbon.management.port}" used in identity.xml is getting
evaluated to NIO port in APIM. We can see that IdentitUtil class[1]
resolves this variable.
I think instead of using your own variable here, we can use
"mgt.transport.https.port" system variable which is already a
