Per Manoop:

From: TATTAVARADA, SUNDER (SUNDER)

Sent: Tuesday, August 28, 2018 6:00 PM

To: LANDO, MICHAEL <ml636r@intl.att.com>; SONSINO, OFIR <os0695@intl.att.com>; MAHER, RANDA <rx196w@att.com>; MIR, FARHAN N (FARHAN) <fmir@research.att.com>

Cc: TALASILA, MANOOP (MANOOP) <talasila@research.att.com>; SHI, LEIMENG <ls3297@att.com>

Subject: AAF Integration using SDK

Importance: High

Hello Team,

We are still in the process of integration CADI framework in SDK to talk to AAF. We already have the capability to communicate with AAF for User Role Enforcement via REST.

We strongly recommend that you start upgrading the current version of SDK to 2.4.0 ( available in staging repository). Our team can help with the upgrade process. Once the CADI integration is fully implemented in 2.5.0 version, at that point it will be easier to just bump your POM to 2.5.0 from 2.4.0 as we are not anticipating any changes in the client code (by design).

Please note. You are already aware of this but just to confirm:

1. SDK will be used for User/Role enforcement only as it is doing today (when user accesses the application from browser). For Casablanca, we are not targeting System to System AAF Authorization.
2. Certificate Management is the responsibility of individual Applications and not SDK.