IBM Support

PJ34950: BP8.LOG IS FLOODED WITH THE ERROR "USER 'XXXXXXX' DOES NOT HAVE A DEFAULT SECURITY PROFILE ASSIGNED"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Description of Problem (full details) :
    The bp8.log is flooded with the error "User 'xxxxxxx' does not
    have a default security profile assigned".
    Is there a workaround? :
    Yes. The error is resolved after manually assigning default
    profile to the newly created user by editing the USERS table in
    the Bp8Metastore database using RDBMD-specific tools.
    Can the problem be replicated on an internal system?  Y or N :
    Y
    By Who (L3, Support, etc..) :
    L3 and Support
    Steps to Reproduce:
    1. Enable bp8.log with debug option turned on
    2. Create a new LDAP user(FileNet-P8Admin) and assign it to all
    the BPF groups.
    3. Try to log in to BPF and choose the default profile.
    4. Review the bp8.log. The log is flooded with the below
    errors:
    2008-03-01 12:31:11,927 ERROR [WebContainer : 1]
    com.filenet.bp8.api.impl.MetadataStore (getUserProfile0:3212) -
    com.filenet.bp8.api.UserDefaultProfileException: User
    'FileNet-P8Admin' does not have a default security profile
    assigned.
     at
    com.filenet.bp8.api.impl.MetadataStore.getUserProfile0(Metadata
    Store.java:3179)
     at
    com.filenet.bp8.api.impl.MetadataStore.getUserProfile(MetadataS
    tore.java:3135)
     at
    com.filenet.bp8.toolkit.server.base.SignInPolicy.setCredentials
    (SignInPolicy.java:126)
    Actual Results:
    The log is flooded with errors "User 'xxxxxxx' does not have a
    default security profile assigned"
    Expected Results:
    This error should not be occurring as the new user has not yet
    had a chance to select a default security profile.
    

Local fix

Problem summary

  • BPF Web Application usersBP8.LOG IS FLOODED WITH THE ERROR "USER
    Description of Problem (full details) :
    The bp8.log is flooded with the error "User 'xxxxxxx' does not
    have a default security profile assigned".
    Is there a workaround? :
    Yes. The error is resolved after manually assigning default
    profile to the newly created user by editing the USERS table in
    the Bp8Metastore database using RDBMD-specific tools.
    Can the problem be replicated on an internal system?  Y or N :
    Y
    By Who (L3, Support, etc..) :
    L3 and Support
    Steps to Reproduce:
    1. Enable bp8.log with debug option turned on
    2. Create a new LDAP user(FileNet-P8Admin) and assign it to all
    the BPF groups.
    3. Try to log in to BPF and choose the default profile.
    4. Review the bp8.log. The log is flooded with the below
    errors:
    2008-03-01 12:31:11,927 ERROR [WebContainer : 1]
    com.filenet.bp8.api.impl.MetadataStore (getUserProfile0:3212) -
    com.filenet.bp8.api.UserDefaultProfileException: User
    'FileNet-P8Admin' does not have a default security profile
    assigned.
     at
    com.filenet.bp8.api.impl.MetadataStore.getUserProfile0(Metadata
    Store.java:3179)
     at
    com.filenet.bp8.api.impl.MetadataStore.getUserProfile(MetadataS
    tore.java:3135)
     at
    com.filenet.bp8.toolkit.server.base.SignInPolicy.setCredentials
    (SignInPolicy.java:126)
    Actual Results:
    The log is flooded with errors "User 'xxxxxxx' does not have a
    default security profile assigned"
    Expected Results:
    This error should not be occurring as the new user has not yet
    had a chance to select a default security profile.
    Upgrade to BPF-4.1.0-001 or above.
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    packages:
    BPF-4.1.0-001
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ34950

  • Reported component name

    BUS PROC FRAMEW

  • Reported component ID

    5724R7500

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-30

  • Closed date

    2008-10-30

  • Last modified date

    2008-10-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    BUS PROC FRAMEW

  • Fixed component ID

    5724R7500

Applicable component levels

  • R410 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNVLC","label":"FileNet Business Process Framework"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
30 October 2008