Logon Screen Configuration Options

The MAFLogonManagerNG.bundle folder contains the MAFLogonOperationContextDefaultValues.plist file, which declares the configuration structure. The plist defines the keys that are used to set default values for the logon scenarios. keyMAFLogonOperationContextDefaultValues is the main key in the default values dictionary. The only screen that supports default values is the registration screen.You can set the default values for the registration screen can be set in the idMAFLogonOperationContextTypeRegister key. Use these keys to set default values for the individual input fields:

To set these values, use code similar to this:

//replace this with your way of accessing MAFLogonUIViewManager->NSObject<MAFLogonNGPublicAPI> (the logon manager public API)
NSMutableDictionary* defaultValues = [logonUIViewManager.logonManager defaultValues]; 

NSMutableDictionary* contextDefaultValues = [defaultValues objectForKey:@"keyMAFLogonOperationContextDefaultValues"];
NSMutableDictionary* registerContextType = [contextDefaultValues objectForKey:@"idMAFLogonOperationContextTypeRegister"];

[registerContextType setObject:@"300" forKey:@" keyMAFLogonOperationContextGatewayClient"];

[defaultValues setObject:contextDefaultValues forKey:@"keyMAFLogonOperationContextDefaultValues"];

You can integrate your own UI solution through the MAFLogonMediator by implementing your own LogonUIViewManager. This is similar to using the default MAFLogonUING implementation, because MAFLogonManagerNG uses context objects to construct the UI:

#import <UIKit/UIKit.h>

@protocol MAFLogonNGPublicAPI;
@protocol MAFLogonUICustomizationDelegate;

/**
 This class handles the navigation between the screens
 */
@interface MAFLogonUIViewManager : NSObject <MAFLogonUIViewManaging, MAFLogonUIViewManagingDelegate>

/**
 The logonMediator where the operations can be initiated. One has to set up the @see logonDelegate to be notified about the result of the operations
 */
@property (readonly) NSObject<MAFLogonNGPublicAPI> *logonMediator;

/**
 The actually presented viewController of the application. This will be used to present the logon related screens.
 */
@property (nonatomic, retain) UIViewController* parentViewController;

The LogonUIViewManager must store a reference to the LogonMediator and the presenting ViewController. The second property presents or dismisses a modal view. To initialize LogonUIViewManager, use:

- (id)init {
    self = [super init];
    if (self) {
        self.logonMediator = [[MAFLogonMediator alloc] init];
        self.logonMediator.logonUIViewManager = self;
    }
    return self;
}

To execute a logon operation, call:

- (IBAction)logonButtonTapped:(id)sender {
	[logonUIViewManager.logonManager logon];
}

MAFLogonManagerNG responds to the request through the MAFLogonUIViewManaging interface:

#pragma mark - MAFLogonUIViewManaging methods

-(void) showViewWithUIContext:(NSMutableDictionary *)aUIContext{
    if([[NSThread currentThread] isMainThread]){
        [self doShowViewWithUIContext:aUIContext];
    }
    else{
        dispatch_sync(dispatch_get_main_queue(), ^{
            [self doShowViewWithUIContext:aUIContext]; //do your custom UI building here!
        });
    }
}
- (void) operationRespondsWithOperationContext:(NSMutableDictionary *)anOperationContext error:(NSError *)anError {
    [currentViewManager operationRespondsWithOperationContext:anOperationContext error:anError];
}
-(void) closeUI {
    [currentViewManager release];
    currentViewManager = nil;
    currentOperationContextType = @"";
    
    [[self baseViewController] popToRootViewControllerAnimated:NO];
    [self.parentViewController dismissViewControllerAnimated:YES completion:^(void){
    }];
}

#pragma mark - MAFLogonUIViewManaging
- (void) operationRespondsWithOperationContext:(NSMutableDictionary *)anOperationContext error:(NSError *)anError {
    [self hideActivityIndicator];
    if (anError != nil && anError.code!=0) {
        [self presentError:anError];
    }
}

Based on the test request response headers, code and cookies, the logon manager decides to use one of these scenarios:

• Direct Gateway
• Direct SAP Mobile Platform server
• SAP Mobile Platform server with relay server
• SAP Mobile Platform server with third-party reverse proxy

If none of these scenarios are true, MAFLogonManagerNG cannot identify the communicator, and generates an error message.

Both of these steps can generate success and failure messages. Error messages are identified by an error code and an error domain, which fits into the iOS error message handling method. You can find definitions for error messages and error codes in the MAFLogonManagerNGErrors.h header file.

#define kErrorDomainLogonManager @"MAFLogonManagerNGErrorDomain"

#define errMAFLogonManagerErrorOperationCancelled           0
#define errMAFLogonManagerErrorInvalidParameter             1
#define errMAFLogonManagerErrorInvalidOperationCode         2
#define errMAFLogonManagerErrorCommunicationManagerError    3
#define errMAFLogonManagerErrorUserAlreadyLoggedIn          4
#define errMAFLogonManagerErrorOperationExecutionInProgress 5
#define errMAFLogonManagerErrorInvalidOperationContext      6
#define errMAFLogonManagerErrorInvalidCommunicatorId        7
#define errMAFLogonManagerErrorInvalidActionItemId          8
#define errMAFLogonManagerErrorCouldNotDecideCommunicator   9
#define errMAFLogonManagerErrorPasswordsNotEqual            10
#define errMAFLogonManagerErrorOperationNotAllowed          11
#define errMAFLogonManagerErrorInvalidServerHost            12
#define errMAFLogonManagerErrorInvalidBackendPassword       13
#define errMAFLogonManagerErrorPasscodeChangeNotEnabled     14
#define errMAFLogonManagerErrorUploadTraceFailed            15