# data[].attributes.body
Fire Chief: Joshua Licudo
Announcements:

Blockers:

Risks:

Goals for the week:

Needs:

# data[].attributes.body
Goals:

Blockers:
Risks:

Mon ★
Last Week:  Finished the week with Artist ID cleanup
Today: In cleaning up the above, found old Opcode related classes still present, confirmed with Shweta this needed to be removed, doing that now. The looking at Permissions, a slowdown of Artist ID queries was reported to David. A little impact is to be expected when switching to Generic Entities, so, looking at simplifying some of the data returned for some of the lists

Tues ★
Yesterday: Old Opcode code cleanup, Artist ID query improvements by data trimming and flow changes on Permissions' side
Today: test of said improvements on dev environments, start looking at modifying the Artist ID page to a progressive scrolling load. Possible cleanup of old LegacyEntitlement code as well, need to verify it's indeed no longer used anywhere

Wed ★
Yesterday: Artist ID fixes. Duplicate issues resolved
Today:  Release of both IGS and Permissions merged masters to QA and pre-prod

Thurs ★
Yesterday: merged Artist ID branches into master and rolled out to QA and pre-prod. Implemented IAM-5567 (createSessionOnRefreshToken), tested locally
Today: merge IAM-5567 into master, deploy to dev and test all providerIds. (maybe roll out to QA and pre-prod?) Deploy IGS/Permissions 1.14.5.0 to Prod?

Fri ★
Yesterday: IAM-5567 work, but I misunderstood some of the reqs, so some of it is wrong
Today : fixing the above, test it

# data[].attributes.body
Goals:

Blockers:
Risks:

Mon 10/23 ★
Last Week: - IAM-5564- MFX Resale system user entitlements completed and merged in master
- IAM-5565- updated logging level for business exception logs in generic exception mapper
Today: - IAM-5565- verified IGS logs, not sure what else can be reduced?
- IGS prod redeployment for 1L

Tues 10/24 ★
Yesterday: - IAM-5565 - IGS logging, to reduce full classpath
- IGS changes for user_search
- identity-service 1.14.4.4 release and prod deployment
Today: - legacy identity command implementation user_search
- 1L verification

Wed 10/25 ★
Yesterday: - IAM-5569: research on legacy identity command user_search
Today: - IAM-5569: continue ^^ user_search command

Thurs 10/26 ★
Yesterday: - IAM:5569: analysis on tmss identity jar to send certificate for user_search command
Today: - IAM-5569: got legacy User and certificate for intdev102 and ijash1, going to try sending certificate details, but as per initial analysis we might need to make changes to tmss jar to send certificate details

Fri 10/27 ★
Yesterday: - IAM-5569: implemented in legacy, but not working yet, looking into assigning permissions to certificate and sending certificate in command
Today : - IAM-5569: looking into sending certificate either in existing jar or somehow in java client

# data[].attributes.body
Goals:

Blockers:
Risks:

Mon ★
Last Week: 1L testing and fixes. New Opcode functionality release to Prod
Today: Updates to Artist ID to increase reload speed. Hammer away at 1L

Tues ★
Yesterday: Tested Artist ID loading.
Today: Doctor's appt in the AM. Continue with Artist ID; make any necessary updates to UI to support API changes.

Wed
Yesterday:
Today: PTO

Thurs
Yesterday:
Today: PTO

Fri
Yesterday:
Today: PTO

# data[].attributes.body
Goals: Roll Out PF integration with TMOne to production, Support session creation in IGS on refresh token.

Blockers:
Risks:

Mon ★
Last Week:  Ticker fix for One login email link should open change password in Ticker app, Ticker team could test in ijash and confirmed functionality.
Today: One login Tirage, roll out. Create Session for user api (Pierre), Token match with TMPS token. Is token validated at app side (signature verification) or just token payload is used(For Salesdeck to query ISMDS)

Tues ★
Yesterday: One login legacy users error messaging and change password support.
Today: One login change password for legacy email users, looked into TMPS identity token and validation, used by ISMDS, CreatsessionforUser, should i create different rest endpoint or same api supporting session creation for B2B/Legacy users along with mfx.

Wed
Yesterday:
Today:

Thurs ★
Yesterday: one login reset password fix for email users legacy, research on token fix for ismds
Today: update pf-datastore jar for create session for user

Fri ★
Yesterday: test one login reset password fix on ijash, pod deployment postponed to Monday
Today: update pf-datastore jar to use new api created by Pierre.

# data[].attributes.body
Goals:

Blockers:
Risks:

Mon  ★
Last Week: 1L + Ticker support; other assorted 1L bugfixes
Today: Last-minute support for 1L launch tonight

Tues ★
Yesterday: 1L launch
Today: Capture errors from legacy identity on 1L and implement expected behavior on legacy/expired password

Wed ★
Yesterday: Legacy expired password 1L flow in production; generic error messaging for failed getUserByUsername/authenticate
Today: Legacy password reset 1L flow; open for more fixes

Thurs
Yesterday: Started on legacy password reset for 1L; deployed to intdev102
Today: Capture legacy auth. error for password reset and continue workflow as expected; deploy to at least preprod by EOD

Fri ★
Yesterday:
* 1L legacy password support in preprod
* Rigor alerts earlier this morning; restarted production 1L
Today:
* Enhance 1L logging for easier issue resolution; review Splunk usage

# data[].attributes.body
Goals:

Blockers:
Risks:

Mon
Last Week:
Today:

Tues
Yesterday:
Today:

Wed
Yesterday: Email design
Today:
Revision of GIF animation for One login announcement email

Continue on illustration & other visual design for email template

Thurs
Yesterday:
Today:

Fri
Yesterday:
Today :