本文介绍了生成授权过程的作用是什么,什么是配置文件?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在尝试了解 SAP 中的授权概念时,我遇到了生成"授权导致配置文件编号的阶段.

While trying to understand the Authorization concept in SAP, I came across the stage where an Authorization is 'generated' resulting in a profile number.

现在我有以下问题:

第一季度.生成"授权是什么意思.按钮实际上有什么新功能,因为我们已经为一个类分配了一个授权对象.我认为这只是为了将授权分配给用户?

Q1. What is the meaning of 'generating' an authorization. What new does the button actually do because we already have allocated an authorization object to a class. I think this only should serve the purpose of allocating this authorization to a user?

第 2 季度.什么是个人资料?

Q2. What is a profile?

谢谢!

推荐答案

配置文件"是内核读取以实际评估权限的技术资料.在 The Good (?) Old Days [TM] 中,只有手动维护的配置文件.角色/活动组稍后建立在此之上,添加了功能和更多设置.因此,它们从那里组装的设置中生成配置文件.这允许从手动配置文件逐渐过渡到生成的配置文件/角色,而不会丢弃已知可以工作的内核和用户代码.您仍然可以在技术名称中看到这一点:PRGN = 配置文件生成器...

"Profiles" are the technical stuff that the kernel reads to actually evaluate the permissions. In The Good (?) Old Days [TM], there were only profiles, maintained manually. Roles / Activity groups were built on top of this later on, adding functionality and more settings. They consequently generate profiles from the settings assembled there. This allowed for a gradual transition from manual profiles to generated profiles / roles without throwing away the kernel and user code that was known to work. You can still see this in the technical names: PRGN = profile generator...

这篇关于生成授权过程的作用是什么,什么是配置文件?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-03 06:40