ContributionsMost RecentMost LikesSolutionsRe: Username / password auth via post request Well that's not secure, encrypted storage though - considering an expression file is just a plain-text file. Storing the data in an account actually encrypts the password field ... which i'd consider the minimum requirement for credential storage ... Re: How do I extract data from an API, using a post request, with the HTTP Client snap? How did you handle the secure storage of the initial credentials (client_id, client_secret)? I've found this to be an impossible task with http client snaps - and hence had to revert to rest snaps for the initial auth - which allows some basic account types to provide the password as `account.password` and `account.username` in the post body. For now, i've however not found an alternative for this with http-client. Re: Regular keyboard navigation in edit box not working correctly it's been almost two years now ... has this received any priority? i realize it's still not available .. but this is a major usability slump... I've in the meantime also opened a support issue about this - but it's en-par with my recent bad experiences with support, which is that they aim to close tickets without even trying to assist. Re: Username / password auth via post request yeah i did - unfortunately to no avail, as "account." is unknown in the http client snap Re: Username / password auth via post request well that's kindof the opposite of what i need the endpoint i need to connect to doesn't accept Basic auth - but requires the username / password to be provided via post body. Username / password auth via post request We've got a service that needs authentication via Post/Put request with the following body: ``` { "U":"someUsername", "P":"someSecurePassword", "L":"EN" } ``` Now with the rest post snap, i can store the data in a "basic auth" account, and use the following: ``` '{ "U":"' + account.username + '", "P":"' + account.password + '", "L":"EN" }' ``` now reading the Rest Api documentation, it is pointing me to use the HTTP client - which i tried, but this doesn't seem to give this option? is there any way to accomplish the same thing with the HTTP client snap? Re: Problems with pipeline and expression library file attachments in Community. Hi Diane, I've tried the "zip" workaround this morning, but it seems like that's also not working. Is there an actual, working workaround ... ? Re: JSON STRING VALUES INTO COLUMNS I think your initial problem is that the data is not actual json. Field separators should be ":" - and the parenteses are clearly off. Snaplogic will still however allow you to do this (you can probably condense this into one mapper if you give it a bit more thought ...): first mapper: `$String.split('},{')` 2nd mapper: `$splitValue.replace('{', '').replaceAll('}}}', '').split(', ').toObject(x => x.split('=')[0], x => x.split('=')[1])` The json splitter in between just splits the data into multiple rows. File-reader encoding I’m having some problems combining file-reader with “convert to document”. My setup is pretty simple - a file-reader that’s reading a document from sldb After the file-reader, the file still seems to have the correct encoding (notice the Ä and Ü ). Converting the file into a string (i need the full document in the content field) - it’s suddenly got ‘Ü’ insead of Ü, and a few other differences. The “convert to document” snap doesn’t seem to have an encoding field … so i’m kinda stuck on how to accomplish this without messing up the file. SolvedRe: Date.now() but with current timezone I wouldn’t have the “asTimezone” method output a string - but just convert the actual date to be in the correct timezone (the output would still be a date object).