Open nbenn opened 11 months ago
Hello,
Thank you for your report. I will forward this issue to the architects. The internal issue number is OUI-2550
Kind regards
@nbenn have you tried to set this config ?
constructor(
private readonly interceptorConfig: ObHttpApiInterceptorConfig,
) {
this.interceptorConfig.api.url = 'http://my-app.com';
}
I'm still checking if I can add a whitelist for pams endpoints but at least your have a workaround.
@ice-blaze Thanks for the feedback. Yes, this is what I have been doing. It took me a bit to figure out that the spinner-interceptor was causing my issues. As soon as I had that sorted, the problem was easy to address. My comment was more to save others from the troubles I had (either via some comment in the docs or a smarter default behavior).
Migrating an Oblique app from the ePortal-provided "header widget" to the oblique-native "service navigation" I ran into CORS issues (with calls to the PAMS API). It appears that
ObHttpApiInterceptor
(with default configuration) andObEportalCsrfInterceptor
are currently not compatible. A quick note on this in the docs or a default config forObHttpApiInterceptor
that does not intercept PAMS API calls might be helpful.