Search found 1414 matches
- Wed Aug 22, 2018 11:47 pm
- Forum: LiveCode Builder
- Topic: Timer not working
- Replies: 3
- Views: 6462
Re: Timer not working
@Greg could you report this?
- Tue Aug 21, 2018 2:03 am
- Forum: LiveCode Builder
- Topic: Built-in properties
- Replies: 13
- Views: 14566
Re: Built-in properties
For each of these properties search their name in the dictionary and you will see you can do things like:
Code: Select all
set the size of my font to 20
Code: Select all
set the red of the color of my background paint to 1
- Wed Mar 21, 2018 12:33 am
- Forum: Bug Triage
- Topic: difference in script editor, missing a few pixels and a crash
- Replies: 11
- Views: 6076
Re: difference in script editor, missing a few pixels and a crash
Hi Folks Yes source code pro is now used as the default script editor font. Using a monospaced font in the script editor can make a significant difference to performance so we decided to bundle an open source font designed for coding to be the default. You can of course change this to whatever you w...
- Wed Feb 15, 2017 2:05 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Regarding the cancelled page you could ask them why that is not going to the redirect URI if the same code is logging in and sending credentials to the redirect URI. That's different to the other services. The example was just for slack yes. Once you have the auth token you would need to set the Aut...
- Mon Jan 30, 2017 11:41 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
If things are working right the Cancel button should close the window. The redirect should handle cancel too.
State will already have a random UUID
State will already have a random UUID
- Mon Jan 30, 2017 12:34 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Hmm... have you setup the redirect URI for this new app? Instead of redirecting it appears to load an error page.
- Mon Jan 30, 2017 12:28 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Hi There was an issue in your code. You can't set the value of a script local like that. Try this (I get a login page with this!): constant kAuthURL = "https://authorization.sandboxcerner.com/tenants/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/protocols/oauth2/profiles/smart-v1/personas/provider/authorize"...
- Thu Jan 26, 2017 2:58 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
The problem is the authentication is being rejected before it even has a chance to present the login page. That's why you get the dialog flashing up. So we need to work out what's wrong with the parameters.
My reading of it is it must be `launch/profile` rather than just `launch` in the scope.
My reading of it is it must be `launch/profile` rather than just `launch` in the scope.
- Thu Jan 26, 2017 12:52 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Aha! So it looks like there's an extra step involved here http://docs.smarthealthit.org/authorization/ See the section labeled SMART “launch sequence” I presume you need the Standalone launch sequence So you must request the metadata in order to get the OAuth endpoints (perhaps there's a reason not ...
- Tue Jan 24, 2017 4:17 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Hi @newpie
It should be something like:
It should be something like:
Code: Select all
local tParamA
put "whatever the aud url is" into tParamA["aud"]
OAuth2 kAuthURL, kTokenURL, kClientID, kClientSecret, kScopes, kPort, tParamA
- Fri Jan 20, 2017 2:44 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
@newpie you could copy the whole file or just edit your version to comment out those lines
- Wed Jan 18, 2017 6:04 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Here's the patch to the OAuth2 library. https://github.com/livecode/livecode/pull/5082
- Wed Jan 18, 2017 5:59 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Looking at the docs here http://docs.smarthealthit.org/authorization/ I see that you need an additional `aud` parameter: URL of the EHR resource server from which the app wishes to retrieve FHIR data. This parameter prevents leaking a genuine bearer token to a counterfeit resource server. (Note: in ...
- Sun Jan 15, 2017 11:24 pm
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
I don't think the smart launch URI is anything to do with OAuth.
I presume when you are testing this you are setting the client secret in your script.
Try changing it to `return "OAuth error:" & the result for error` so you can see what error is being returned by the server.
I presume when you are testing this you are setting the client secret in your script.
Try changing it to `return "OAuth error:" & the result for error` so you can see what error is being returned by the server.
- Fri Jan 13, 2017 5:43 am
- Forum: Getting Started with LiveCode - Experienced Developers
- Topic: OAuth2 token Help needed
- Replies: 25
- Views: 30752
Re: OAuth2 token Help needed
Hi @newpie Many APIs require you to set a redirect URI server side and failing to do so or setting it incorrectly will result in the redirect uri mismatch error. In this case you need to set it to: http://127.0.0.1:443/. There should be some method available to do so in the api console where you got...