I understand to verify that a bank is not asking more than one set of MFA questions, you must check the results from each discoverAndAddAccounts call, but IPP AggCat for .Net also offers the discoverAndAddAccountsResponse method. Can this method also pass back the new Challenge/Response questions? If so, how, and if not, when would this method ever be used?
Thanks for any help in advance.
The latest release, 1.3.0, has an additional overload to DiscoverAndAddAccountsResponse that passes back challenge questions and session to handle multiple MFA rounds. Please see:
https://developer.intuit.com/docs/0020_aggregation_categorization_apps/devkits
Related
I'm looking for a way how to add custom ignore parameter via api. I.E. api equivalent of this UI screen
I'm afraid thats not supported by the API at the moment :(
Could you raise an enhancement request for that?
https://github.com/zaproxy/zaproxy/issues/new
I'm happy to do that for you, but if you do it then you'll get notified when we start working on it etc.
Thanks, Simon
I am new to swift.
I am now trying to implement crashlytics in to my app.
I have followed the tutorial to implement it for basic report but I want to implement userID so that I know who has problem using my app.
I have checked online and found setUserIdentifier function but I have no idea where to implement this function.
Do I need to call this function in every page or in app delegate.swift?
Please give me an example on how to implement this one function.
Thank you very much.
let phoneID = UIDevice.currentDevice().identifierForVendor.UUIDString
Fabric.with([Crashlytics()])
Crashlytics.sharedInstance().setUserIdentifier(phoneID)
I used this to solve the problem and get the phone id.
I would strongly discourage the #Jun-Luo 's approach of using UUUID.
Crashlytics.sharedInstance().setUserIdentifier("12345")
Crashlytics.sharedInstance().setUserEmail("mail#domain.com")
Crashlytics.sharedInstance().setUserName("AppUserName")
You can use any one of above to track the user. But its better to secure user privacy, hence all we need as a developer is a ID which we can easily tack back with our server side access.
Code Example
https://docs.fabric.io/apple/crashlytics/enhanced-reports.html
here is a old version:https://wiki.jasig.org/display/CAS/Using+CAS+without+the+Login+Screen
I need to do the same with that latest version of CAS i.e. 3.5 . Can anyone provide me the steps for the same
We are doing now basically what you're asking here in my company. We have a Sharepoint website that in background is using the RESTful services for doing the real login. I wrote some posts about them in my blog and recently we used it to get access from a iOS application which contains a link to a sample program.
Important!!! We have a modification in our CAS that offers the possibility to use it for more than one domain. So wherever you find a reference to something called "Domain" in my samples just remove it, as it will not work on standard CASes
Here is a nice solution to your problem.
Just enable restful access.
I have currently written code to send an email in C# using the usual SMTPClient and MailMessage objects.
My new requirement is that the email being sent should have "permissions" set as if the user was sending the email via Outloook and using the option from the ribbon toolbar. The permission to be set is the "Do Not Forward" option.
The option I wish to emulate when sending the email is accessed here;
Can anyone please supply some sample .Net code to achieve this or else provide me with a good code reference online?
Thanks in advance,
Brian.
First of all, I am unaware as to how one might be able to set IRM (Information Rights Management) permissions using only a standard SMTP message (MailMessage). IRM permissions, I believe, are completely Outlook/Exchange-centric, and lack any sort of representation in the SMTP standard.
The only way you're going to be able to enable that permission is through the Outlook Object Model via the Outlook Interop assemblies. IamStalker above me recommended Redemption, which, while 99% of the time is the correct answer for everything Outlook-related, is not the way to go for this particular problem. Because IRM (as far as I know) has no representation in MAPI, Redemption wouldn't be much help here; I don't believe I've ever seen an IRM-related property on Redemption's object model.
You'll most likely be interested in the Permission property exposed by the MailItem object type. It appears that in order to programmatically turn on the "Do Not Forward" option, you will want to set the value of that property to OlPermission.olDoNotForward.
There is another IRM-related property (PermissionTemplateGuid), but it appears that you can leave this as an empty string since you are using a built-in "permission".
I would assume then that all other IRM-related settings are provided to Outlook through the user's Outlook profile.
Good luck!
Hello Brian I have only one suggestion "Redemption"!
I have used it and it's awesome it's very easy to implement the owner Dima is very nice person
he helps alot.
PS: It's not free but worth every penny.
Why isn't the TerminateWithSuccess method of the SharedApplication implemented in MonoTouch? How can I invoke it? or even better, how can I programmatically close the application?
terminateWithSuccess is private API, which is why MonoTouch does not surface it. You should still be able to call it by using a Selector.
Selector s = new Selector("terminateWithSuccess");
UIApplication.SharedApplication.PerformSelector(s, UIApplication.SharedApplication, 0)
FWIW- I received this last week- Looks like the time is UP for this method...
Thank you for submitting your update to xxxx to the App Store. During our review of your application we found it is using private APIs, which is in violation of the iPhone Developer Program License Agreement section 3.3.1; "3.3.1 Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs." While your application has not been rejected, it would be appropriate to resolve this issue in your next update.
The following non-public APIs are included in your application:
terminateWithSuccess
If you have defined methods in your source code with the same names as the above mentioned APIs, we suggest altering your method names so that they no longer collide with Apple's private APIs to avoid your application being flagged with future submissions.
Please resolve this issue in your next update to xxx.
After posting the question i figured it out, but Matt beat me to it. Here's another way:
UIApplication.SharedApplication.PerformSelector(new Selector("terminateWithSuccess"), null, 0f);