I'm attempting to override access token expiry time dynamically (on a client-by client-basis), per the accepted answer in this question. Upon overriding the expiry time in ValidateClientAuthentication, the "expires_in" field does not show in the response anymore.
Can anyone clarify why that may be and how to get it back?
Thanks
My bad.
I had an invalid value set for the value of ExpiresUTC.
Related
I am attempting to get user stories from instagram graphAPI.
Query_hash is instagrams hashed version of the query string params.
Does anyone who has been working with Instagrams private API have any idea which variables are passed in to this query_hash? Trying to get users stories and query_hash is required. At one point rhx_gis and user-agent were part of query_hash. Now rhx_gis is no longer a used variable and user-agent to the best of my knowledge is no longer required as part of the hash.
Example hash and variables:
e769aa130647d2354c40ea6a439bfc08
{"id":"8500884","first":12,"after":"QVFCLVRNU3ZtWlBOcHJTb09LaEprekpoQXo0OE9ZV0lXVUM5MU9jSmZadHdjRFdyT1BUVlFCVnhkbWFuRmYtUDZrN3NPeTJWTGhWWEh0emNTU0VHcnpHLQ=="}
I tried adding everything I can think of but the md5 always comes out differently than the query_hash. Hoping someone has figured this out!
I have question regarding Intent configuration in Dialogflow.
I've found information on StackOverflow regarding ".recent" attribute of sys.date parameter.
The idea is that using value from that attribute gives a date that happened in the past (i.e. "Monday" will be translated to last Monday, not next Monday).
I've encountered a problem when using it with required parameters.
The result in date interpretation differs depending on the input:
has the user provided all required parameters at once
user has been prompted to deliver missing ones.
Please find example below - notice different dates returned for the same input
Intent configuration
Behavior
Questions:
Do you know what may be the problem here? It seems like a bug for me
I've searched and I have not been able to find documentation on
Dialogflow's or Google's sites regarding ".recent" - do you know
where I can find it?
When I create a new record on the Service Request (SR) application (Maximo 7.6), I would like to set the required Reported Date (SR.REPORTDATE) field blank. Before save action, the user will input data into that field. I wonder how this could be done?
Thanks for the help.
If you look in Database Configuration to see if REPORTDATE has a Default Value, I think you'll find &SYSDATE& in there. If I'm right, then you can delete that default value, save your changes, and apply your changes. Otherwise, you'll need to do as #Dex suggested.
My mind immediately goes to an automation script. A default value control or the default value setting in Database Configuration may work too and is recommended before a script if you have the expertise to confirm or deny this theory.
As for the automation script, I think you can create one with an object launch point on SR on the "add" event. The script would simply set that field to null, which shouldn't change the "required" flag either, so the rest of your needs will still be met.
mbo.setValueNull("REPORTDATE");
Currently I'm facing this issue after implementing SecurityManager. A simple gist of what I did was, create an object with populated values if an user logins. If another user logins, I would overwrite one specific variable in the previous user's object. Then I proceed to stop server and starts it again. When I check through pulse, my two objects are there as expected but that one specific variable reverted to its initial value before the second user logins. It's the same for subsequent users. Any helps are appreciated.
Requires region.put(retrieved object's key, the retrieved object) back instead of just object.setVariable().
What's the difference between NSLocale currentLocale vs autoupdatingCurrentLocale? It's not obvious from reading the documentation.
When the user changes their system locale settings, the autoupdating one automatically updates to the new locale.
The currentLocale only retrieve an locale object one time from the current user's settings. autoupdatingCurrentLocale updates the locale object on the fly so you don't need to validate. You might think autoupdateingCurrentLocale is the prefer way, it is per Apple documentation; however, since the returned object may be cached, you don't really need to hold on to it indefinitely when using currentLocale, verse autoupdateingCurrentLocale.
If you are using autoupdatingCurrentLocale, note that this API do not cache the locale object, so you will need a way to compute cache upon receipt. One way is to use notification such as NSCurrentLocaleDidChangeNotification method call.