When you attempt to log on to the SAS Information Delivery Portal, the following error might occur in the browser:

Incorrect Logon

The portal log might contain the following error:

l.delegates.authentication.LogonDelegate - Access Denied 

[WARN ] sas.portal.metadata.omr.OMRPortalProfile - [ERROR] 
l.delegates.authentication.LogonDelegate - Could not find portal profile in 
repository omi://xxxxxxxx.xxx.xx.xxx:8561/A0000001.A5XXXXXXnull; nested exception is: 
com.sas.services.ServiceException: Could not find portal profile in 
repository omi://xxxxxxxx.xxx.xx.xxx:8561/A0000001.A5XXXXXXnull at 
com.sas.portal.metadataOperations.AuthenticationMetadataFacade.loadPortalProfileForUser 
(AuthenticationMetadataFacade.java:83)

Caused by: com.sas.services.ServiceException: Could not find portal profile 
in repository omi://xxxxxxxx.xxx.xx.xxx:8561/A0000001.A5XXXXXXnull at 
com.sas.portal.metadata.omr.OMRPortalProfile.init(OMRPortalProfile.java:415)

The preceding errors will occur if a user that has previously logged on to the SAS Information Delivery Portal has been deleted from the User Manager in the SAS^® Management Console and then added back in.

This deleting and adding back might have occurred if the SAS bulk-load macros are being used to add users into the User Manager. The bulk-load macro determines if an existing identity was created manually or with the bulk-load macro. If the existing identity was created manually, the bulk-load macro will fail. Therefore, the identities are being manually deleted in order for the bulk-load macro to run successfully.

To correct the problem, perform one of the following suggestions:

1. Do not delete the user from User Manager unless the user is to be permanently removed from the system. Instead of deleting the user from the User Manager, add an ExternalIdentity object to manually entered users prior to running the synchronization process of the bulk-load macro. Refer to SAS Note 30860 for details.
2. After deleting the user from User Manager, restart the application server before adding the user back. Restarting the application server will clean up the original metadata pertaining to the user. Therefore, when the user is added back in, it is treated as a new user. Note that any portal pages and other content in the portal that is associated with that user will be gone.
3. If the user has already been deleted and added back to the User Manager, then an attempt can be made to correct the current Portal Permission Tree permissions for this user. There is no guarantee that this will work. In SAS Management Console, expand the following tree views:
• Authorization Manager
• Resource Management
• By Application
• BIP Service
• Portal Application Tree

Find the portal permission tree with the user's name associated with the specific user. Right-click that permission tree and select Properties. Select the Authorization tab.

Locate the entry for this same user's name on the Authorization tab. Review the permissions granted and denied for that user. Note that this user should be listed for its own permission tree and should be explicitly granted ReadMetadata and WriteMetadata permissions, which means there is a check mark under GRANT for these two permissions and the check box does not have a colored box (grey or green) around it.

Select the PUBLIC group from the same authorization tab. PUBLIC should have an explicit deny for the ReadMetadata and WriteMetadata permissions.

Now select the Portal Admins group from the same authorization tab. The portal admins group should have an explicit grant for the ReadMetadata and WriteMetadata permissions.

Operating System and Release Information