Capacitor Logging In but then getting unauthorised on Api's

[jmartland22]

Wonder if anybody could help. I have been able to log in using a android mobile app with capacitor. I can return user name etc… from the same api action.

When I try to run any other api actions I get unauthorised response. I have got my security provider set to set to secure and samesite = none.

On the mobile app I have the credentials ticked on the api actions.

Could anyone point me to what I am missing.

Thanks,

[nomad]

@jmartland22

When I try to run any other api actions I get unauthorised response.

What authorization setup are you using? Have you checked to be sure that the API has access to the credentials or token so it can run later?

I’m kind of making guesses, I think a little more info about your setup and exact error conditions would help narrow it down.

[jmartland22]

Thanks. I am just using standard security provider.

Then I am using Capacitor and calling this API to login. This is successful. At the end of this API I get some user details which come through fine. When I check though no cookie is set.

I then on success run a API to get some more data. I get the below response and no data through.

I have ran another API that doesn’t need you to be logged in to view and this is working fine so I think it’s something to do with the cookie not being set but I am really not sure. I have tried adding this to the config but with no luck.

I am running the mobile app on Android Studio. If I switch over to Cordova everything works okay. Any help would be brilliant I’ve been going round in circles on it for a few days but it’s all over my head.

[bpj]

Make sure you tick the ‘credentials’ checkbox on each server connect component on your page

There is a FR to make it ticked by default for mobile projects:

Enable credentials on Server Connect by default option

Could a project option be added (particularly useful for mobile apps) to have the credentials option enabled by default when adding SC to a page? I’m finding that I keep forgetting. Being a bit slow these days, it takes a few moments to work out what is causing the ‘unauthorized’ response which slows the whole design/build process. It would just be really useful as it will be required for every one I add in this project.

[jmartland22]

Thanks @bpj. Just voted for this

I have ticked the credentials on all the server connect components. Have you been able to get Capacitor to work in this way in any of your projects?

[jmartland22]

Just wondering @Teodor is this possible in Wappler at the moment using Capacitor (Cordova works okay) to set cookies without adding lots of manual code? Or is there a way around using Capacitor for API actions behind a security provider / restrict?

Thanks,

[jmartland22]

I have been looking further and on my site the cookie is saying samesite=strict. I have set the samesite to none (see below). I have redeployed to DigitalOcean numerous times. Is this correct or could this be the problem?

[bpj]

I don’t think the samesite setting applied properly:

Handling cookies for Mobile App

W5.1.4 Mobile App It seems that the option to set the sameSite property in security provider has no impact - looking at the provider.js file, it appears that it only allows true/false in a falsy expression (line 22) this needs to allow the value of the sameSite setting e.g. ‘None’ e.g. sameSite: opts.sameSite || 'Strict',

[jmartland22]

Thanks. Yeah think your right. Did you find a workaround or just waiting for a update?

[bpj]

I manually adjusted the provider.js file as detailed in the post

[jmartland22]

Thanks so much

That solves the problem. Capacitor is now working as expected.